Infinite error loop when pushing stash from GUI #3133
Comments
|
Following as I started having this issue in the past week. Uninstalled/reinstalled GitLens to no avail, every time I stash I end up with a bazillion duplicate stashes. GitLens Version14.9.0 VS Code VersionVersion: 1.88.1 Git Versiongit version 2.39.2 The built-in source control context menu's "Stash" option works fine, it's just the GitLens select files -> right click -> "Stash changes..." command that goes into an infinite loop until VS is killed. I don't have anything getting logged to the output panel though when this happens. |
|
This issue might be possibly related to #2953, as it happens in the same type of repos that the other bug happens as well. |
|
I'm having this issue as well. VSCode Version InfoVersion: 1.90.1 (user setup) Git Versiongit version 2.34.1.windows.1 |
|
This is the third time it happens to me, and I keep falling for it (and keep retrying an apparent no-op) I think it consistently happens when you try to stash the staged area when a file has staged and local changes on the same line.
Quick remedy: |
Usually it happens to me when i do the first stash so I just use |
|
Thanks for reporting this. I have not been able to reproduce the error where it creates infinite stashes with the details provided. Thank you! |
I had commented that it might be related to a different issue in this comment. They seem to happen in the same types of repos. In #2953 a user was able to identify which types of repos this happens on: link to post here. While this particular repo is in dropbox, i have had the issue on other repos as well that are not being synced. EDIT: Formatting. |
|
We've pushed a change that resolves a possible loop with stashing though we believe it is unrelated to this issue, it would be great if you could try out tomorrow's ( It would also be great if anyone else who can reproduce this could provide logs and details as to what button/command you are using to stash the changes. /cc @tjesposito @nwazuo @MarkJeronimus @MarkJeronimus In the scenario you suggested, stashing staged changes when a file has the same line changed in both the index and working tree, are you seeing this modal? Can you also provide details as to what button/command you are using to stash the changes? You can switch to the pre-release edition of GitLens, by clicking on the "Switch to Pre-Release version of this extension" from the Extensions view.
|
|
Eric and crew, excellent news- I'm no longer getting the stash loop. Hadn't tried since reporting in June (for fear of infini-stashing), so I don't know exactly where the issue resolved. But my current specs are: GitLens Versionv2024.10.1805 (pre-release) VS Code VersionVersion: 1.94.0 Git Versiongit version 2.45.0 Thank you for looking into it and getting it resolved somewhere along the line. Note that compared to an earlier comment, in my case I was having problems even with nothing staged (just a plain ol' clear-the-desk before switching branches on our repo) |
|
I stash with the small "Stash All Changes..." button next to the "Staged changes" fold-out.
|
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
When trying to use the
Stash All Changesbutton from theSource Controltab from GitLens, the tool enters an infinite loop creating stashes due to an error. All of them stash the full file and not the diff.The only way to stop is to close VSCode and re-open it.
I could not reproduce the problem on a clean repository, and this issue happens with some of my repositories, not all.
I do not know where to start troubleshooting.
GitLens Version
14.7.0
VS Code Version
Version: 1.85.2 (system setup)
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:10.514Z
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621
Git Version
git version 2.43.0.windows.1
Logs, Screenshots, Screen Captures, etc
I get a lot of stashes like this:
The output window repeats the following error:
The file exists and is accessible and not locked as far as I can tell.
Output Log -- Debugging Enabled for GitLens
The text was updated successfully, but these errors were encountered: