Since lazy_file got enabled, opening a file with a line number using wsdjeg/vim-fetch now gives errors on startup

[lparry]

Ever since this commit I've been seeing errors on startup any time I open a file with a line number

eg

$ nvim path/to/some_file.rb:20

Error executing vim.schedule lua callback: ...ocal/share/nvim/lazy/LazyVim/lua/lazyvim/util/plugin.lua:99: Invalid buffer id: 1
stack traceback:
        [C]: in function '__index'
        ...ocal/share/nvim/lazy/LazyVim/lua/lazyvim/util/plugin.lua:99: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>
Press ENTER or type command to continue
Error executing vim.schedule lua callback: ...ocal/share/nvim/lazy/LazyVim/lua/lazyvim/util/plugin.lua:83: Vim:E367: No such group: "lazy_file"
stack traceback:
        [C]: in function 'nvim_del_augroup_by_name'
        ...ocal/share/nvim/lazy/LazyVim/lua/lazyvim/util/plugin.lua:83: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

The correct file is opened at the correct line, but the errors are kind of annoying.

Can someone please fill me on what I need to change to make this error go away? Or even just how to disable lazy_file in config instead of modify the lazyvim source in ~/.local?

[lparry]

realised this is probably the wrong repo for this question, sorry
!