Skip to content

fix: propagate idle timeout to accepted Remoters - #164

Open
kentbull wants to merge 2 commits into
ioflo:mainfrom
kentbull:fix/remoter-tymeout-propagation
Open

fix: propagate idle timeout to accepted Remoters#164
kentbull wants to merge 2 commits into
ioflo:mainfrom
kentbull:fix/remoter-tymeout-propagation

Conversation

@kentbull

@kentbull kentbull commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Propagate the Server-configured idle tymeout to accepted TCP and TLS Remoter instances. Supervisors can then expire stale accepted connections through the existing cleanup gate instead of treating timeout as disabled.

The regression exercises timeout propagation and expiry through virtual scheduler time.

Fixes #167

@kentbull

kentbull commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

The maintained 0.6 adaptation is merged as GLEIF-IT#2.

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
Document that the WASM smoke test verifies native-only persistence backends are not imported eagerly.

This is a test-contract clarification and keeps the assertion intent clear while refreshing CI for the pull request.
@kentbull kentbull changed the title fix: restore idle TCP connection cleanup fix: 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.

Configured TCP idle timeout is not applied to accepted connections

1 participant