[5.4] Queue worker will pass connection + queue name to Looping event #18975
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.
This allows the
Queue\Events\Looping
to pass along the connection and queue names. I was working on some more detailed logging/status monitoring of different job processors for queues across multiple servers, and realized there was no easy way to hook onto this (I didn't want to hook onto theJobProcessing
hook as this was too noisy)I wrote a basic test as well, but it was somewhat hacky so I didn't include (there are also currently no other tests that look for the Looping event anywhere currently). I can include in comments if you think it would be useful.
Basic example of what I was trying to accomplish below. Please let me know if you think this is unnecessary/overkill and/or a better approach