-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add tests for websocket close #9071
Conversation
This is a followup to add more coverage for #5180
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 #9071 +/- ##
=======================================
Coverage 98.30% 98.30%
=======================================
Files 107 107
Lines 34390 34405 +15
Branches 4075 4074 -1
=======================================
+ Hits 33806 33821 +15
Misses 412 412
Partials 172 172
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.10: 💚 backport PR created✅ Backport PR branch: Backported as #9075 🤖 @patchback |
(cherry picked from commit a33270b)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9076 🤖 @patchback |
(cherry picked from commit a33270b)
This is a followup to add more coverage for #5180
It took me a while but I realized that this is behaving as expected because the client is sending a string
await ws.send_str('some data')
which is never received by the server (noreceive
), and the connection is closed while the message is still on the wire.Everything is working as expected, and the test was wrong.
closes #5180