tests: Ensure transaction callbacks run in FIFO order #56973
Merged
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.
DatabaseTransactionsManager
allows registering callbacks withaddCallback()
. The intended behavior is that these callbacks should run in the same order they were added. While existing tests cover that callbacks are executed, there was no explicit test guaranteeing ordering semantics. Without a regression guard, an internal implementation change could unintentionally reverse or reorder callbacks.