Description
- Gitea version (or commit ref): 1.3.2
- Git version: 1.8.3.1
- Operating system: CentOS 7
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No (because it's a commercial product)
- Not relevant
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.
We don't have any plugins or instandard stuff, just a Gitea's binary, the DB, and repos.
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:
