Skip to content

backport: propagate idle timeout to accepted Remoters - #2

Merged
kentbull merged 3 commits into
release/v0.6.20from
backport/remoter-tymeout-propagation-v0.6.20
Aug 24, 2026
Merged

kentbull merged 3 commits into
release/v0.6.20from
backport/remoter-tymeout-propagation-v0.6.20

Conversation

@kentbull

@kentbull kentbull commented Aug 24, 2026 •

Copy link
Copy Markdown
Collaborator

Adapts ioflo/hio#164 to the GLEIF Python 3.12-compatible 0.6 maintenance line.

Propagate the Server-configured idle tymeout to accepted TCP and TLS Remoters so supervisors can expire stale connections through the existing cleanup path.

Base: published HIO 0.6.19 commit 3daa9bfa7bd714276f08219b91abd1914d8b6428.

Propagate the server configured idle tymeout to accepted TCP and TLS Remoters. Without that value, supervisors treat idle expiration as disabled and leave stale connections active.

Add regression coverage that advances virtual time and exercises the normal idle cleanup gate on the Python 3.12-compatible 0.6 maintenance line.
Bring the merged UDP loopback test correction into this branch so CI evaluates the Remoter tymeout backport against the current 0.6.20 release base.
Merge release/v0.6.20 at bde6319 so this PR is tested with the accepted-socket recovery change already merged into the release line.
@kentbull
kentbull merged commit 9aa4656 into release/v0.6.20 Aug 24, 2026
3 checks passed
@kentbull
kentbull deleted the backport/remoter-tymeout-propagation-v0.6.20 branch August 24, 2026 18:16
@kentbull

kentbull commented Aug 28, 2026 •

Copy link
Copy Markdown
Collaborator Author

Backports the fix for ioflo#167 to release/v0.6.20. The corresponding upstream implementation is ioflo#164.

@kentbull kentbull changed the title backport: restore idle TCP connection cleanup for 0.6 backport: propagate idle timeout to accepted Remoters Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant