-
Notifications
You must be signed in to change notification settings - Fork 3.1k
fix(next): prevent transaction race condition in renderDocument parallel operations #14652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
jessrynkar
approved these changes
Nov 18, 2025
Contributor
|
🚀 This is included in version v3.65.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Fixes
MongoExpiredSessionErrorcaused by transaction state mutation leaking between parallel operations inrenderDocument.Problem
When
renderDocumentrunsgetDocumentPermissionsandgetIsLockedin parallel viaPromise.all, they share the samereqobject. WhengetDocumentPermissionscallsdocAccessOperation→initTransaction(), it mutatesreq.transactionID. This mutation is visible togetIsLocked, which then tries to use the same transaction. When the permission check completes and commits its transaction,getIsLockedfails with an expired session error.This is because
getIsLockedmay still be trying to use the transactionID it (involuntarily) received fromgetDocumentPermissions, even thoughgetDocumentPermissionsalready closed it.Solution
Use
isolateObjectProperty(req, 'transactionID')to give each parallel operation its own isolated transaction state. This creates a Proxy wheretransactionIDmutations go to a delegate object instead of the shared parent req.If parent
reqalready has a transaction, it's preserved (no isolation applied).Testing
This PR does not include tests, as it's very difficult to reliably test for this race condition. I reproduced this issue using this PR: #14631 as it just happened to speed up
getDocumentPermissionsjust enough to trigger this race condition more often.