Repository navigation
fix(nestjs): Isolate BullMQ lifecycle handlers - #25533
Draft
nicohrubec wants to merge 2 commits into
Draft
nicohrubec wants to merge 2 commits into
nicohrubec wants to merge 2 commits into
Conversation
Co-Authored-By: OpenAI GPT-6 <codex@openai.com>
Contributor
size-limit report 📦
|
…le scopes Co-Authored-By: OpenAI GPT-6 <codex@openai.com>
This branch has not been deployed
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
1 participant
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.
BullMQ lifecycle listeners currently write to the default isolation scope, leaking breadcrumbs into unrelated HTTP requests. Share the processor scope with job-related worker hooks using the worker's
Jobinstance, and isolate queue notifications and worker-wide hooks per invocation.Keep the processor's existing exception capture. Lifecycle listeners only manage isolation and preserve application error handling. Regression coverage checks shared worker context, async queue notification isolation, and propagation of synchronous and asynchronous listener errors without capture.
Fixes #19765.