-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.3.2 beta has a UI Loop when checkout in isn't possible #9297
Comments
@NickCraver Thanks for filing. Marking this as a bug pending further investigation. tags: spinning, looping, loops, spins, endless |
Also experiencing this bug in Version 2.5.3. The UI gets stuck just as demonstrated above, and has the same git error.
|
Another report of this #7718 (comment):
|
From the logs above, these are the errors I spotted. This issue seems related to #7691, #4592, #8064, and #9434
The video may hold some clues. I could not reproduce. |
From #10733:
|
@steveward Try going to the command line and checking out the branch. If you get an error there and it specifies the problem file, then you can just delete that file and you should be able to switch branches. |
@Listbd I was the submitter on #10733. For me, this is very intermittent but the next time it happens (which has been days or weeks apart) I can try that and provide some additional info here. Regardless, I'd still expect the GUI to error handle whatever the issue is properly. Edit to clarify: I have tried to purposefully recreate this without luck but I have seen it multiple times. |
I was able to reproduce this today. When I try to check out in the command-line I do get an error:
If I
The upstream is gone because it was squashed and merged. I'll create a new clone for my work and leave this in place for any further info gathering. |
@CliffWMiller Just to confirm, have you also been using @NickCraver What's your typical way to get yourself out of that scenario when you do get into it? I've never had to use |
@niik Edit: I lied. I looked through the scripts for the project and that is done to these files. |
@CliffWMiller Thank you so much for confirming, I think I have a pretty clear understanding of what's going on now! I am looking into how we can prevent the loop from occurring and I hope to have something ready for review soon to remedy that. I did read up on assume-unchanged/skip-worktree and food this interesting note in the Git documentation.
All that to say is that I think Desktop's solution here will need to be to surface the error from Git and let users who manually update this bit to resolve the situation outside of Desktop. |
Describe the bug
When trying to checkout a PR, it goes into a fun loop retrying the checkout but not presenting an error (screenshot below).
At the console, here's what the error was:
Note that the 2 files in question do not show as pending differences, because they have both been:
(this is because Redis stores state in the config, and we shouldn't be updating master with that state constantly)
This combination seems to confuse the UI and it doesn't present an error...it just gets in a fun loop. Closing the app is the only way I've found to escape it.
Version & OS
OS: Windows 10
Client: 2.3.2-beta5
Steps to reproduce the behavior
See above description...unfortunately not trivial to reproduce. But it's possible this repros without any PR needed on any branch checkout.
Expected behavior
User gets an error indicating why checkout isn't possible.
Actual behavior
Infinite merry-go-round loop of fun!
Screenshots
Logs
Logs have sensitive data from our GHE instance, but the only related bits are this in a loop:
Hope this helps!
The text was updated successfully, but these errors were encountered: