backport: reset Remoter idle timeout from current tyme - #7
Merged
kentbull merged 2 commits intoAug 27, 2026
Merged
Conversation
Use Tymer.start() so successful I/O refreshes inactivity from the current scheduler tyme instead of accumulating duration from the previous stop. Cover repeated refreshes and recovery after expiration.
Skip idle timer reset until a Remoter has an injected scheduler tyme. This preserves untimed TCP and HTTP use while Tymer.start() governs configured inactivity.
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
1 participant
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.
Adapts the focused correction from ioflo/hio#168 to the maintained 0.6.20 line.
Remoter.refresh()now resets inactivity from current scheduler tyme instead of extending from the previous deadline, while remaining a no-op without an injected time base.Upstream issue: ioflo/hio#169