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
Revision graph broken (regression) #11700
Comments
@mstv I can make a PR to revert to my previous version of the optimization that don't introduce the regression. |
I have seen similar artifacts, too, mostly after rebase operations. I had two suspects: the commit identified by you or #11205.
That variant had other issues. I think this will be resolved by the planned graph rendering in the background. Give me a few weeks for this rewrite, please. |
Environment
Issue description
At least on repository opening (I don't know if it could happen during a refresh)
it seems only when the repo has unrelated histories (but not sure)
the graph is broken:
instead of expected:
Refreshing the repository seems to make the bug disappear...
Steps to reproduce
No clear steps:
Did this work in previous version of GitExtensions?
Bisected to 609e03d, so yes, before
Diagnostics
Handling of
e.Handled
is too aggressive?The text was updated successfully, but these errors were encountered: