-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
feat(replay): Debug replay summarizer failure #93714
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
In Seer access logs, Seer responds with a 200, but this endpoint is somehow returning a `ParseError`. Add some logging when status_code is not 200.
}, | ||
) | ||
|
||
response.raise_for_status() |
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.
idk I see the other seer endpoints use this instead -- maybe we're getting a <400 status code?
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.
Probably overkill with the log above but its fine. This is internal any way.
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## master #93714 +/- ##
==========================================
+ Coverage 86.89% 88.03% +1.14%
==========================================
Files 10324 10326 +2
Lines 595768 595926 +158
Branches 23137 23137
==========================================
+ Hits 517672 524640 +6968
+ Misses 77603 70793 -6810
Partials 493 493 |
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
In Seer access logs, Seer responds with a 200, but this endpoint is somehow returning a `ParseError`. Add some logging when status_code is not 200.
In Seer access logs, Seer responds with a 200, but this endpoint is somehow returning a
ParseError
. Add some logging when status_code is not 200.