Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

E367: No such group "--Deleted--" in Explorer:destroy when core.init is re-entered during a git runner wait

Ouverte
  • Quelque chose ne va pas ?
#3,363 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
git, lua, neovim
Domaine
tooling

Piste de recherche

Start with lua/nvim-tree/explorer/init.lua around Explorer:destroy and new, then trace the reentrant initialization through lua/nvim-tree/core.lua and the git runner wait. Reproduce with the two repositories and delayed git wrapper from the issue. Done when changing the tree root to /tmp/nvt-b during the wait no longer raises E367.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug reproduced
Description

Opening a file in a directory that is not under the tree root can fail with:

E367: No such group: "--Deleted--" at explorer/init.lua:81 (Explorer:destroy)

The failure is intermittent. It occurs when a global :cd (e.g. from
project.nvim on BufEnter) changes the working directory to another project
while the tree is rooted elsewhere. A slow git status (large repository) makes it more likely.

Neovim version
NVIM v0.12.6
Build type: RelWithDebInfo
LuaJIT 2.1.1788856981
Operating system and version

Linux 7.2.9-arch1-1

Windows variant

No response

nvim-tree version

master 355bcc8

Clean room replication
vim.g.loaded_netrw = 1
vim.g.loaded_netrwPlugin = 1

vim.cmd([[set runtimepath=$VIMRUNTIME]])
vim.cmd([[set packpath=/tmp/nvt-min/site]])
local package_root = "/tmp/nvt-min/site/pack"
local install_path = package_root .. "/packer/start/packer.nvim"
local function load_plugins()
  require("packer").startup({
    {
      "wbthomason/packer.nvim",
      "nvim-tree/nvim-tree.lua",
      "nvim-tree/nvim-web-devicons",
    },
    config = {
      package_root = package_root,
      compile_path = install_path .. "/plugin/packer_compiled.lua",
      display = { non_interactive = true },
    },
  })
end
if vim.fn.isdirectory(install_path) == 0 then
  print("Installing nvim-tree and dependencies.")
  vim.fn.system({ "git", "clone", "--depth=1", "https://github.com/wbthomason/packer.nvim", install_path })
end
load_plugins()
require("packer").sync()
vim.cmd([[autocmd User PackerComplete ++once echo "Ready!" | lua setup()]])
vim.opt.termguicolors = true
vim.opt.cursorline = true

-- MODIFY NVIM-TREE SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
_G.setup = function()
  require("nvim-tree").setup({
    -- legacy `update_cwd = true` migrates to this
    sync_root_with_cwd = true,
    -- legacy `update_focused_file = { enable = true, update_cwd = true }` migrates to this
    update_focused_file = { enable = true, update_root = { enable = true } },
  })

  -- simulate project.nvim, which performs a global :cd to the project root on BufEnter
  vim.api.nvim_create_autocmd("BufEnter", {
    callback = function()
      if vim.bo.buftype == "" and vim.fn.filereadable(vim.fn.expand("%:p")) == 1 then
        vim.schedule(function()
          vim.cmd("cd /tmp/nvt-b")
        end)
      end
    end,
  })
end
Steps to reproduce

Two git repositories are necessary: the tree is opened in the first and a
file is edited in the second. A git wrapper delays every git invocation by
200ms to deterministically widen the race window between the 15ms debounce
and the git job; on a sufficiently large/slow repository the wrapper is not
required.

mkdir -p /tmp/nvt-a /tmp/nvt-b
cd /tmp/nvt-a && git init -q && git commit -q --allow-empty -m a
cd /tmp/nvt-b && git init -q && echo x > f.txt && git add f.txt && git commit -qm b
mkdir -p /tmp/nvt-bin
printf '#!/bin/sh\nsleep 0.2\nexec git "$@"\n' > /tmp/nvt-bin/git
chmod +x /tmp/nvt-bin/git

cd /tmp/nvt-a
PATH=/tmp/nvt-bin:$PATH nvim -nu /tmp/nvt-min.lua

In neovim,

  1. :NvimTreeOpen
  2. <C-w>p to focus the original window (tree open, not focused)
  3. :edit /tmp/nvt-b/f.txt
Expected behavior

Tree root changes to /tmp/nvt-b without error.

Actual behavior
vim.schedule callback: .../nvim-tree.lua/lua/nvim-tree/explorer/init.lua:81: Vim:E367: No such group: "--Deleted--"
stack traceback:
	[C]: in function 'nvim_del_augroup_by_id'
	.../nvim-tree.lua/lua/nvim-tree/explorer/init.lua:81: in function 'destroy'
	.../nvim-tree.lua/lua/nvim-tree/core.lua:19: in function 'init'
	.../nvim-tree.lua/lua/nvim-tree/explorer/init.lua:806: in function 'force_dirchange'
	.../nvim-tree.lua/lua/nvim-tree/explorer/init.lua:839: in function 'change_dir'
	.../nvim-tree.lua/lua/nvim-tree/actions/tree/change-root.lua:42: in function 'fn'
	.../nvim-tree.lua/lua/nvim-tree/actions/tree/find-file.lua:62: in function 'fn'
	.../nvim-tree.lua/lua/nvim-tree/autocmd.lua:68: in function 'callback'
	.../nvim-tree.lua/lua/nvim-tree/utils.lua:351: in function <.../nvim-tree.lua/lua/nvim-tree/utils.lua:350>
	[C]: in function 'wait'
	.../nvim-tree.lua/lua/nvim-tree/git/runner.lua:209: in function 'wait'
	...
	.../nvim-tree.lua/lua/nvim-tree/explorer/init.lua:75: in function 'new'
	.../nvim-tree.lua/lua/nvim-tree/classic.lua:186: in function <.../nvim-tree.lua/lua/nvim-tree/classic.lua:184>
	.../nvim-tree.lua/lua/nvim-tree/core.lua:30: in function 'init'
	.../nvim-tree.lua/lua/nvim-tree/explorer/init.lua:806: in function 'force_dirchange'
	.../nvim-tree.lua/lua/nvim-tree/explorer/init.lua:839: in function 'change_dir'
	.../nvim-tree.lua/lua/nvim-tree/actions/tree/change-dir.lua:11: in function 'fn'
	.../nvim-tree.lua/lua/nvim-tree/autocmd.lua:55: in function <.../nvim-tree.lua/lua/nvim-tree/autocmd.lua:54>
	[C]: in function 'nvim_exec2'
Langage dominant
Lua
Étoiles
8.7k
Forks
639
Merge moyen
8 h 25 min
PR mergées (30 j)
3

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nvim-tree/nvim-tree.lua

Toutes les issues de nvim-tree/nvim-tree.lua

Issues similaires

Plus d'issues Lua

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.