API error after upgrading from 4 to 5.0

[Chris Hightower]

After upgrading from ReviewBoard 4 to 5.0, when trying to use the API, we receive a 500 response.

Visiting http://reviewboard.mydomain.com/api  gives the following:

ImproperlyConfigured at /api/

More than one URI template was mapped to the "commits" name: http://reviewboard.mydomain.com/api/repositories/{repository_id}/commits/, http://reviewboard.mydomain.com/api/review-requests/{review_request_id}/diffs/{diff_revision}/commits/.

Each URI template must be mapped to a unique URI template name in order to be included in the URI templates list. This can be set through the uri_template_name property.

This looks like an issue in the web server configuration, but I don't know how to look/fix that.  Any tips or ideas?

Thanks

[Christian Hammond]

It looks like a bug in Review Board with some new validation that was out in.

We have a release planned for next week, which fixes possible issues here. This one hasn’t come up in our testing, but I’ll try to reproduce this and make sure it’s working before release.

What version of Python is the server running?

Christian

--
Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups "Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/889713a7-c93a-46fd-88bb-390983eb58cdn%40googlegroups.com.

--

--
Christian Hammond
President/CEO of Beanbag
Makers of Review Board

[Chris Hightower]

Python 3.8.10 on Ubuntu 20.04.05 LTS

Thanks for looking into it! You guys are awesome!

[Christian Hammond]

I just realized, if you're getting an actual error here, you must have Debug mode turned on, which isn't good for production. In the event of a conflict, there should be a log error, not a failure to load the URL.

Check your site's conf/settings_local.py and make sure this is still present:

    DEBUG = False

Christian

To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/5cdaf9fa-c6c4-4f2b-a260-1865f4a7722fn%40googlegroups.com.

[Chris Hightower]

Changing DEBUG back to False fixed the API.

Thanks for the help.