-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
fix(stack-trace): Forward 403 Errors #26597
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
Conversation
|
This pull request 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 label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
ad48961 to
e840a7d
Compare
ceorourke
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, maybe @NisanthanNanthakumar will have more context here though since it's stacktrace linking related. I'm not sure this actually fixes the linked Sentry issue (is that the right one? because it seems to be plugin issues about Pushover).
39947ab to
3dc66cb
Compare
|
@NisanthanNanthakumar I just rebased this branch can you take another look? |
size-limit report
|
cb36402 to
195ee70
Compare
Fixes SENTRY-QQG.
There is an unhandled exception in stacktrace links when the user's GitHub account is suspended.