Fix MongoDB session lifecycle management in synced adapter #80
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.
MongoDB sessions were not being properly cleaned up after transactions, causing session leaks. Sessions were only ended in
close(), not aftercommitTransaction()orabortTransaction().Changes
Session lifecycle fixes:
commitTransaction()andabortTransaction()now callsession.endSession()and clear the session referencegetSession()now properly stores newly created sessions inthis.sessionType safety:
session: ClientSessiontosession?: ClientSessionto eliminate unsafe type castsUsage
The
getSession()method is already public and can be used for custom operations within transactions:Added comprehensive documentation and examples for manual transaction control and session lifecycle patterns.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.