Rework how the conn timeout stuff works #7
Merged
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.
The consumer will wrap each reserve (and other commands) up in a context timeout of 3 seconds. However, this timeout is started before it has acquired the lock of a beanstalk connection.
This PR removes the context timeouts for those specific commands and moves the timeout to a config variable that is set after having acquired the lock of a connection. Timeouts in contexts are still honoured, if present.