Skip to content

fix: restore idle TCP connection cleanup - #164

Open
kentbull wants to merge 1 commit into
ioflo:mainfrom
kentbull:fix/remoter-tymeout-propagation
Open

fix: restore idle TCP connection cleanup#164
kentbull wants to merge 1 commit into
ioflo:mainfrom
kentbull:fix/remoter-tymeout-propagation

Conversation

@kentbull

@kentbull kentbull commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Accepted TCP and TLS Remoters did not receive the server-configured idle tymeout. Their effective timeout remained 0.0, so supervisors treated idle expiration as disabled and left stale connections active.

This change propagates the configured timeout and adds a regression that advances virtual time and exercises the idle cleanup gate.

Verification

  • PYTHONPATH=src pytest -q tests/core/tcp
  • 14 passed

Fixes #167

@kentbull

Copy link
Copy Markdown
Contributor Author

If we want to do a 0.6.x release then this is easily cherry-pickeable to a 0.6.x branch, we just need to make said branch.

Propagate the server's 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.

Fixes ioflo#167
@kentbull
kentbull force-pushed the fix/remoter-tymeout-propagation branch from 54d429e to b96ac98 Compare August 19, 2026 19:43
@kentbull kentbull changed the title fix: timeout -> tymeout Remoter arg fix: restore idle TCP connection cleanup Aug 19, 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.

Configured TCP idle timeout is not applied to accepted connections

1 participant