We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Often times this happens on application startup. It has happened to be but also has been reported by users on discord: https://discord.com/channels/1060193121130000425/1073202153163857920/1293975411684016128 https://discord.com/channels/1060193121130000425/1206670506271707156/1295647968803815424
My hypothesis is that this is a race condition getting BranchListingDetails for branches while the app is fetching from the remote
BranchListingDetails
NB: It appears that the error is harmless, but it can be quite noisy especially if there were many merged branches
The text was updated successfully, but these errors were encountered:
FYI it seems to happen on every app launch as well, even when there are no changes on remote. See recording: https://cln.sh/XTrhxKPj
Sorry, something went wrong.
As one would expect, this is a gitoxide error, but the prefix seems to be added in the frontend, judging from the find_reference() calls in the backend.
gitoxide
find_reference()
This makes me think that the hex-hash prefix is the name of the branch, but I am not sure.
I could look into this if I could get a hint on how to reproduce the issue.
No branches or pull requests
Often times this happens on application startup. It has happened to be but also has been reported by users on discord:
https://discord.com/channels/1060193121130000425/1073202153163857920/1293975411684016128
https://discord.com/channels/1060193121130000425/1206670506271707156/1295647968803815424
My hypothesis is that this is a race condition getting
BranchListingDetails
for branches while the app is fetching from the remoteNB: It appears that the error is harmless, but it can be quite noisy especially if there were many merged branches
The text was updated successfully, but these errors were encountered: