vscode: Git Commit Ament caused "Git: connect ENOENT" error

I had the same issue and the problem on my side was that $XDG_RUNTIME_DIR did not exist. For some reason the WSL Ubuntu set it to a non-existent /run/user/1000. I fixed the error by creating the directory like this:

sudo mkdir /run/user/1000/
sudo chown 1000:1000 /run/user/1000/

and issuing a Reload Window.

I think there is some error in some clean-up logic that accidentally removes the folder instead of the socket, which would explain why it breaks intermittently. Just a theory, I didn’t have the time to investigate.

I’ve noticed, for me at least, the error only occurs if you leave the commit message blank. If you write a new commit message before pressing amend it works.

So maybe the error happens with the file that opens where it prompts you to edit the previous commit message?

Same here, It can only be restored to works by restarting vscode, and still occurs several times a day.

> git -c user.useConfigOnly=true commit --quiet
→ No staged files match any configured task.
Error: connect ENOENT /var/folders/_v/rdq8cmks24jgvtkk5sypbgw00000gn/T/vscode-git-0698a41bdc.sock
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'connect',
  address: '/var/folders/_v/rdq8cmks24jgvtkk5sypbgw00000gn/T/vscode-git-0698a41bdc.sock'
}
error: There was a problem with the editor '"/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/git/dist/git-editor.sh"'.
Please supply the message using either -m or -F option.

It seems no issue anymore in Version: 1.83.0 according to tested myself and it looks gone

@unional In my case quitting and relaunching VSCode helps.

Just encounter this again. And quitting VScode does not fix it.

even running wsl --shutdown does not fix it.

@unional In my case quitting and relaunching VSCode helps.

Same problem in 1.82.2