Fix Connection Pool crash when requests are waiting while timer is triggered#474
Draft
lovetodream wants to merge 8 commits intovapor:mainfrom
Draft
Fix Connection Pool crash when requests are waiting while timer is triggered#474lovetodream wants to merge 8 commits intovapor:mainfrom
lovetodream wants to merge 8 commits intovapor:mainfrom
Conversation
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
2 participants
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.
When connections are requested from the pool in bursts, the pool might have requests in the queue while a keep alive or idle timer is triggered. This should resolve the issue, closes #472.
Currently, I've only implemented a test case to reproduce the behaviour. (The test case is a bit verbose atm, but I wanted to include the full picture for now)
One way to fix it would be to check the request queue in
PoolStateMachine.connectionKeepAliveTimerTriggered(_:)andPoolStateMachine.connectionIdleTimerTriggered(_:)instead of a precondition. This can be archived by callingPoolStateMachine.handleAvailableConnection(index:availableContext:)if the queue is not empty.Maybe this should be handled in
ConnectionPoolinstead?Let me know what you think @fabianfett