-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Unknown
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
Go Drivers
-
Not Needed
-
-
None
-
None
-
None
-
None
-
None
-
None
Detailed steps to reproduce the problem?
When command logging is enabled at the debug level, commitTransaction and abortTransaction commands are not being logged, even though they should be according to the Command Logging and Monitoring specification. The spec only excludes handshake and heartbeat commands from logging.
https://gist.github.com/prestonvasquez/9a48c5853369f2e01490d429372f3704
Definition of done: what must be done to consider the task complete?
The Session.AbortTransaction() and Session.CommitTransaction() methods in mongo/session.go must be updated to call .Logger(s.client.logger) when constructing their respective operations, ensuring the client's logger is propagated to the transaction commands.
The exact Go version used, with patch level:
$ go version
The exact version of the Go driver used:
go version go1.25.0 darwin/arm64
Describe how MongoDB is set up. Local vs Hosted, version, topology, load balanced, etc.
NA
The operating system and version (e.g. Windows 7, OSX 10.8, ...)
OSX 15.7.2
Security Vulnerabilities
NA
- causes
-
GODRIVER-3760 Add unified spec tests for commitTransaction and abortTransaction command logging
-
- Closed
-