Repository navigation
test: add queue receive timeout integration coverage (framework#1568) - #157
Closed
goravel-coder wants to merge 1 commit into
Closed
goravel-coder wants to merge 1 commit into
goravel-coder wants to merge 1 commit into
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
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.
Summary
queue.connections.<connection>.timeoutbounds the blocking receive aDriverWithReceiveworker performs.databaseconnection with"timeout": 5so the example demonstrates the new option.github.com/goravel/frameworkto the PR #1568 commit so the suite exercises the new behavior end-to-end.Why
This adds integration coverage for goravel/framework#1568, which makes a queue worker's blocking receive timeout configurable per connection. Previously the wait was fixed, so receive-based drivers could not tune how long a worker blocks before polling again.
The example now documents the new option and pins the framework to the PR commit, so the timeout is exercised through a real worker against a
DriverWithReceivefake that records the deadline it is handed.