You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.
Intermittently, I receive a index.lock file exists error when I try to add-all-and-commit
Steps to reproduce:
Cmd+Shift+P to Engage the command palette
Choose Git Plus: Add All Commit and Push
See error message from git that index.lock file exists
Aftermath
When I go to the file system there is no index.lock file there. The system is left in the state where the file has been added but nothing else has been executed. This suggests that there is a race condition whereby the commit command is being issued before the add finishes and so it sees an index.lock file while I don't (because by the time i see the file system, add would have completed). Is there some way to sequentialize the commands? Maybe they are being fired off as three async processes that can execute simultaneously?
The text was updated successfully, but these errors were encountered:
Intermittently, I receive a index.lock file exists error when I try to add-all-and-commit
Steps to reproduce:
Aftermath
When I go to the file system there is no index.lock file there. The system is left in the state where the file has been added but nothing else has been executed. This suggests that there is a race condition whereby the commit command is being issued before the add finishes and so it sees an index.lock file while I don't (because by the time i see the file system, add would have completed). Is there some way to sequentialize the commands? Maybe they are being fired off as three async processes that can execute simultaneously?
The text was updated successfully, but these errors were encountered: