Draft:[12.x] Fix CallQueuedClosure::displayName after batch chain (#57597) #57881
+67
−1
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 fixes a fatal error (
Call to undefined method Closure::getClosure()) when a Closure is placed immediately after a Bus::batch call within a Bus::chain.The issue arose because the Closure object was passed as a raw
\Closureinstance toCallQueuedClosure::displayName, which incorrectly assumed it was always wrapped in aSerializableClosureand tried to callgetClosure().This patch adds a check to safely extract the underlying Closure, preventing the crash.
Fixes #57597