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
There're not so many branches that a currently simultaneously used (around 6-7), however the overall number of branches is 28. Something started to go wrong today then the git graph stopped to display correctly—there're no more colors at all. Below are the screenshots of the problem.
Unfortunately I really cannot give more info about the problem because our development process haven't changed for a long time: We just commit and push and very often review this git graph on out instance of Gitea. And out of the blue it gets white with an error in JS console.
My first assumption was that it may be connected with the fact than each new branch gets it own color, and maybe there's a finite number of colors to display, however 28 branches isn't a limit at all for a bit project... So I do believe the assumption is wrong.
Screenshots
The result of something goes wrong with git graph:
What the developer tools in Chrome outputs regarding the error:
The direct place in the JS file where the error occurs:
The text was updated successfully, but these errors were encountered:
After a new commit was added, the graph started to display entirely. However, when one more was added, is once again started to the crooked in the same way, directly to the same place as in the previous screenshot.
The regularity of this may be important: When the test branch is the very upper one, then this gets crooked; otherwise it works. So it isn't clear whether this relates to the number of total branches or still something else.
The original issue comes from Gitea: go-gitea/gitea#3382
But still I'm duplicating the text:
Description
There're not so many branches that a currently simultaneously used (around 6-7), however the overall number of branches is 28. Something started to go wrong today then the git graph stopped to display correctly—there're no more colors at all. Below are the screenshots of the problem.
Unfortunately I really cannot give more info about the problem because our development process haven't changed for a long time: We just commit and push and very often review this git graph on out instance of Gitea. And out of the blue it gets white with an error in JS console.
My first assumption was that it may be connected with the fact than each new branch gets it own color, and maybe there's a finite number of colors to display, however 28 branches isn't a limit at all for a bit project... So I do believe the assumption is wrong.
Screenshots
The result of something goes wrong with git graph:
What the developer tools in Chrome outputs regarding the error:
The direct place in the JS file where the error occurs:
The text was updated successfully, but these errors were encountered: