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
{{ message }}
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.
I am noticing errors come through to Sentry that have the wrong Request URL for the Handler that gets called.
The specific situation I am seeing in Sentry is Handler3 being called for a request to /two/user_1234.
The other strange thing is Handler2 is called hundreds of times per minute. But the error is raised infrequently (a couple hundred times in the past 5 days)
I have tried to replicate this locally but as I cannot mimic the functionality.
Given the implementation below is it possible that a error raised from a request is being tagged with the wrong Request URL?
If this is not the case I will move on to the gorilla/mux issues.
Using gorilla/mux v1.6.1
I am noticing errors come through to Sentry that have the wrong Request URL for the Handler that gets called.
The specific situation I am seeing in Sentry is
Handler3
being called for a request to/two/user_1234
.The other strange thing is Handler2 is called hundreds of times per minute. But the error is raised infrequently (a couple hundred times in the past 5 days)
I have tried to replicate this locally but as I cannot mimic the functionality.
Given the implementation below is it possible that a error raised from a request is being tagged with the wrong Request URL?
If this is not the case I will move on to the gorilla/mux issues.
The text was updated successfully, but these errors were encountered: