"exec: Stdout already set" when staging a file

[HannesOlszewski]

Describe the bug
Left lazygit open for a while so I don't know what exactly lead to this. After some coding I wanted to stage my files with space and the error "exec: Stdout already set" was shown. No file was staged. Restarting lazygit did not help and I needed to delete .git/index.lock to resolve this.

To Reproduce
Steps to reproduce the behavior:

1. Stage file with space
2. See error

Expected behavior
The file being staged and no error shown.

Screenshots

Desktop (please complete the following information):

• OS: MacOS 12.2 (M1)
• Lazygit Version: v0.32.2
• The last commit id if you built project from sources: Not applicable, installed through Homebrew

[jesseduffield]

On master I've fixed the issue with the error not being very informative, however the index.lock bug remains. Haven't been able to determine what's causing it. Any help is much appreciated!

[simonvizzini]

I just ran into this issue (exec: Stdout already set), and the last thing I did in lazygit before it happened was to rebase my working branch with unstaged changes which resulted in some merge conflicts. What was strange is that this time I didn't get the usual "Merge conflicts! Resolve or press enter to abort" message (don't remember the exact spelling). The merge conflicts were not critical and so I simply reverted the files that contained the conflicts (via lazygits 'd' shortcut). After that I continued to work on my code and when I came back to lazygit (which I always keep open in a terminal window) I couldn't stage files anymore, getting the mentioned "Stdout already exists" error. Not sure if these steps somehow triggered the error, but I hope it helps in identifying the root cause. I'll keep observing it and if it happens again I'll try to provide more details.

Edit: I'm also using lazygit v0.32.2 on Arch Linux

[jesseduffield]

This is fixed in #2765 (it was already fixed but I've fixed it again after adding retry logic for the index.lock issue)