What version are you running?
2.5.17
What's the URL of the page containing the problem?
https://projects/admin/db/scmtools/repository/add/ (new Gitlab project)
https://projects.dx-erkrath.de:8081/r/new/ (existing Gitlab project)
What steps will reproduce the problem?
- create repository with Gitlab private-token
- OR add a new review request on existing repository with same Gitlab private-token
What is the expected output? What do you see instead?
- sucessfully add a new repository
- successfully add a new review reqest to existing repository
both not possible right now
What operating system are you using? What browser?
Chromium
Please provide any additional information below.
The existing repository (#2) was working weeks ago with the very same private-token. It has no expire date set.
I have tried with a newly created private-token, which gives another error: unable to decode base64. Are the hashes produced by Gitlab different now?
When using the existing repository (#1) a trace is written to reviewboard.log, see attachment. Also a decoding problem, I dont see if its the private-token or something else.
one more thing: the existing repo (#2) shows a
HTTP 500 INTERNAL SERVER ERROR
on the reviewboard WebUI. TheHTTP 410: Gone
can only be seen in reviewboard.log
What version of GitLab are you using? If it's one with API v4, you'll need to upgrade Review Board to 3.0.6 or newer.
-
- New + NeedInfo
It's likely that they've turned off the old API endpoints. I believe you'll need to upgrade your Review Board.
updated to 3.0.7 on python 2.7.5 and that repo works again.
However, we had to fix
reviewboard.wsgi
because of the trace attached.The problem is with
import pkg_resources
: it also does__main__.__requires__ ...
which we think makes it crash somehow. Our quick fix without understanding all of it is to import pkg_resources before importing main. That makes it run as far as I can see.
-
+