Avoid writes after lost connection#831
Open
ben-grande wants to merge 1 commit into
Open
Conversation
When the socket connection is lost, "asyncio.selector_events" doesn't raise an exception, but logs warning level when attempting to write to a lost connection past certain threshold. To avoid spurious writes and logs, write only once to allow "QubesDaemonProtocol.connection_lost()" to be called early. Prior to this change, "connection_lost()" was called only after many writes. Fixes: QubesOS/qubes-issues#10923
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #831 +/- ##
==========================================
- Coverage 70.42% 70.37% -0.05%
==========================================
Files 61 61
Lines 14128 14132 +4
==========================================
- Hits 9950 9946 -4
- Misses 4178 4186 +8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Jun 28, 2026
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026070101-devel&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026050504-devel&flavor=update
Failed tests32 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/176874#dependencies 16 fixed
Unstable testsDetails
Performance TestsPerformance degradation:31 performance degradations
Remaining performance tests:80 tests
|
This was referenced Jun 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the socket connection is lost, "asyncio.selector_events" doesn't raise an exception, but logs warning level when attempting to write to a lost connection past certain threshold. To avoid spurious writes and logs, write only once to allow "QubesDaemonProtocol.connection_lost()" to be called early.
Prior to this change, "connection_lost()" was called only after many writes.
Fixes: QubesOS/qubes-issues#10923