-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error not captured by sentry: Invalid request method "OPTIONS" #7185
Comments
If Remix themselves handled this exception and swallowed it there at the current moment there is no way for Sentry to capture it - so it depends on what the framework was doing with the error internally. I assume this was not a unhandled exception (which would crash the server). I agree though we should be capturing these, maybe we can monkey patch |
You're right it didn't crash the server, so I do think it was unhandled. I do see Sentry in that call stack... That might mean Sentry would/could have seen it? |
Yes - let's see if I can quick win handle this case, otherwise will backlog for later. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using? If you use the CDN bundles, please specify the exact bundle (e.g.
bundle.tracing.min.js
) in your SDK setup.@sentry/remix
SDK Version
7.34.0
Framework Version
Remix 1.8.2
Link to Sentry event
No response
SDK Setup
Here is our remix server sentry init:
Also:
And:
Steps to Reproduce
Remix has a regression where it fails to handle OPTIONS requests, and I expected/hoped Sentry would have alerted us to this, instead we didn't get an errors tracked, and hence no alerts or notifications.
In our http logs I see:
Here is the PR where Remix fixed the issue: remix-run/react-router#9914
Expected Result
I expected this error to be caught by sentry so we could be alerted about it. Is there something we need to change in our config to handle this?
Actual Result
No warnings or alerts.
The text was updated successfully, but these errors were encountered: