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
CURRENT BEHAVIOR: When selecting 2-5 repositories at once, an error is thrown saying: application quitted with an unhandled error: same job already is in the queue
EXPECTED BEHAVIOR: When selecting any number of repositories, application continues and other commands may be entered.
So I can get this issue a few ways, and I'm rather new at this so let me know if I'm just using it wrong:
navigate to parent folder of at least 5 repositories in windows Command Prompt or Powershell, (I had 15 repos in the folder when I tested)
enter gitbatch then press enter to open the gitbatch console,
select one repository to fetch by pressing space,
Press down to highlight another repository,
select the other repository by pressing space.
return to step 4 until the error occurs.
If you're fast enough, you can get it to crash after getting the second one, but if you wait, the largest amount of repositories I'd queued in a row was 3 (Powershell) or 4 (CMD) before the error occurred.
My Specs:
The text was updated successfully, but these errors were encountered:
I see this frequently managing ~210 repositories, haven't really found the workaround although it eventually works, but patience is required. I'll try and make some time to debug, but wanted to share that you're not alone in this issue.
CURRENT BEHAVIOR: When selecting 2-5 repositories at once, an error is thrown saying:
application quitted with an unhandled error: same job already is in the queue
EXPECTED BEHAVIOR: When selecting any number of repositories, application continues and other commands may be entered.
So I can get this issue a few ways, and I'm rather new at this so let me know if I'm just using it wrong:
If you're fast enough, you can get it to crash after getting the second one, but if you wait, the largest amount of repositories I'd queued in a row was 3 (Powershell) or 4 (CMD) before the error occurred.
My Specs:
The text was updated successfully, but these errors were encountered: