-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Add human readable error messages for WebSocket PING/PONG timeouts #10422
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
Currently the exception would stringify to an empty string which left the caller with no information about why the WebSocket disconnected in the log
CodSpeed Performance ReportMerging #10422 will not alter performanceComparing Summary
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #10422 +/- ##
==========================================
- Coverage 98.77% 98.76% -0.01%
==========================================
Files 122 122
Lines 37125 37127 +2
Branches 2044 2044
==========================================
- Hits 36669 36668 -1
- Misses 316 319 +3
Partials 140 140
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #10431 🤖 @patchback |
Backport to 3.12: 💚 backport PR created✅ Backport PR branch: Backported as #10432 🤖 @patchback |
… for WebSocket PING/PONG timeouts (#10432) Co-authored-by: J. Nick Koston <[email protected]>
… for WebSocket PING/PONG timeouts (#10431) Co-authored-by: J. Nick Koston <[email protected]>
What do these changes do?
Currently the exception would stringify to an empty string which left the caller with no information about why the WebSocket disconnected in the log
Are there changes in behavior for the user?
Human readable errors
Is it a substantial burden for the maintainers to support this?
no