https://sourceforge.net/apps/trac/sourceforge/ticket/22505
Error 500 occurs on page http://sourceforge.net/p/abonpro/code/ci/3da3e8b80ac410df67d3cd65993270c774e9e6b2/tree/. This happened after pushing initial commit contents into Git repository. Maybe this caused by Readme file with Cyrillic symbols, but I tried UTF-8 encoding and the same error raised too.
This initially showed a 500 error, then I tried refreshing the repo and it seems stuck at "analyzing" now.
That is, it still shows a 500 when trying the exact link the user provided, but https://sourceforge.net/p/abonpro/code/ is stuck at analyzing.
Might be related to [#2698], but both of the other tickets mentioned in that one are closed, so I figured I'd go ahead and log this as a new ticket.
Related
Tickets:
#2698I am seeing this error as well, while running under mod_wsgi, which since the move to 2.7 has opened up a whole can of worms with the GitPython process stuff.
The problem is apparently arising in the template code, which eventually gets down to the git command level. It appears the calling of git.repo.git.branch is causing the issue.
In forgegit.model.git_repo.py, commenting out symbolics_for_commit and letting RepositoryImplementation handle it removes the problem, though the larger problem of not being able to use GitPython in the WSGI process is troubling.
QA:
(on dev)
(on forge:rc/3150 without resetting mongodb or anything)
And if you're really ambitious, you can repeat the 'on dev' steps above except on rc/3150 and observe that crap works.
When this is pushed, you'll need to run
Works as advertised. Merged to dev.
Script was run in prod - repo still stuck in 'analyzing' step.
More updates that should take into account the new-style repository structures
Merged to dev.