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
When no reviewers are configured in the backend's database, the code which randomly selects a reviewer fails, causing the server to return an HTTP 500 error when submitting a new app.
This isn't a major issue since it only occurs when there are no reviewers (which isn't the case in our production environment), but it's annoying to encounter in development environments, so we should return a proper error in the API (and perhaps modify the UI as well) to clearly indicate when there are no reviewers available to assign.
The text was updated successfully, but these errors were encountered:
When no reviewers are configured in the backend's database, the code which randomly selects a reviewer fails, causing the server to return an HTTP 500 error when submitting a new app.
This isn't a major issue since it only occurs when there are no reviewers (which isn't the case in our production environment), but it's annoying to encounter in development environments, so we should return a proper error in the API (and perhaps modify the UI as well) to clearly indicate when there are no reviewers available to assign.
The text was updated successfully, but these errors were encountered: