Skip to content

gh-136234: Fix _SelectorSocketTransport.writelines to be robust to connection loss #136743

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bmerry
Copy link
Contributor

@bmerry bmerry commented Jul 17, 2025

@python-cla-bot
Copy link

The following commit authors need to sign the Contributor License Agreement:

CLA signed

@bmerry
Copy link
Contributor Author

bmerry commented Jul 17, 2025

I've previously signed the CLA on behalf of my organisation, but my work email address has changed since then (same employer though). Is there a process to reuse that form, or do I need to sign a new one? Alternatively, I can rewrite my commits to use that old email address (it still works, just deprecated).

@kumaraditya303
Copy link
Contributor

do I need to sign a new one?

You need to sign again with the new email.

@@ -1048,6 +1048,11 @@ def _read_ready__on_eof(self):
else:
self.close()

def _write_after_conn_lost(self):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only used at two places, I would prefer this to be inlined rather than as a new function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

_SelectorSocketTransport.writelines does not protect against connection lost
2 participants