Fix: rename test route to testerror/
#2702
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I needed this change while testing #2694.
In 746f322, we introduced an
error/
route to core's URLconf. We overlooked that in the root URLconf, there already was anerror/
route ifDEBUG=True
, which is for the purpose of testing Sentry.That change was in May 2024, so I'm not sure how we've been able to test Sentry updates since then. For example, in November 2024, I was somehow able to hit the root
error/
and trigger theRuntimeError("Test error")
.Today, what I saw was that when I go to
error/
, I hit the coreerror/
and see the Error page. No Sentry notification is sent:I had to change the route name to something else in order to hit the root path and then a Sentry notification was sent: