add re-entrancy guard to RootListenersTracer to prevent recursive listener invocations #33745
+76
−26
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.
PR Message
Description:
This change introduces a contextvars-based re-entrancy guard in RootListenersTracer and AsyncRootListenersTracer to prevent listener callbacks (on_start, on_end, on_error) from invoking nested listeners. When multiple custom PII middlewares are stacked, listener implementations may indirectly trigger another chain/graph run and reattach listeners, forming a loop that eventually leads to a GraphRecursionError in LangGraph. The guard blocks listener re-entry within the same execution context, breaking the unintended cycle while preserving normal listener behavior.
Changes:
Rationale:
Backwards compatibility:
Tests/validation:
Issue: GraphRecursionError when adding multiple custom PIIMiddleware #33740