-
Notifications
You must be signed in to change notification settings - Fork 125
Always clear read idle timeout at the end of a request #455
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
Merged
dnadoba
merged 3 commits into
swift-server:main
from
dnadoba:dn-read-idle-timeout-bug-fix
Oct 8, 2021
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,6 +38,7 @@ final class HTTP2ClientRequestHandler: ChannelDuplexHandler { | |
if let newRequest = self.request, let idleReadTimeout = newRequest.requestOptions.idleReadTimeout { | ||
self.idleReadTimeoutStateMachine = .init(timeAmount: idleReadTimeout) | ||
} else { | ||
self.clearIdleReadTimeoutTimer() | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess we should not trigger this here (though recommended by me earlier), but instead trigger a idle state machine event at all places where we cancel/fail the request. |
||
self.idleReadTimeoutStateMachine = nil | ||
} | ||
} | ||
|
@@ -238,17 +239,18 @@ final class HTTP2ClientRequestHandler: ChannelDuplexHandler { | |
self.run(action, context: context) | ||
} | ||
|
||
case .clearIdleReadTimeoutTimer: | ||
if let oldTimer = self.idleReadTimeoutTimer { | ||
self.idleReadTimeoutTimer = nil | ||
oldTimer.cancel() | ||
} | ||
|
||
case .none: | ||
break | ||
} | ||
} | ||
|
||
private func clearIdleReadTimeoutTimer() { | ||
if let oldTimer = self.idleReadTimeoutTimer { | ||
self.idleReadTimeoutTimer = nil | ||
oldTimer.cancel() | ||
} | ||
} | ||
|
||
// MARK: Private HTTPRequestExecutor | ||
|
||
private func writeRequestBodyPart0(_ data: IOData, request: HTTPExecutableRequest) { | ||
|
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, if we should remove this from the state machine tbh. The more I think about it the more I think we should just create another event (requestFailed) or something that removes the timer in the error case. Just calling clearTimer into the air and not syncing with state machine probably leads to out of sync errors in the future.