Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
1
Description
When we dump the TransactionsConfig to the log we attempt to log the custom ATR location. If there is no custom ATR location then the call .Agent() leads to a panic which leads to logs like
Initializing transactions: CustomATRLocation:%!s(PANIC=String method: runtime error: invalid memory address or nil pointer dereference) ExpirationTime:0s
I'm not entirely sure why this doesn't crash the entire SDK.
Attachments
Issue Links
- is cloned by
-
GOCBC-1350 [Backport] Logging can trigger a panic in TransactionATRLocation
-
- Resolved
-
For Gerrit Dashboard: GOCBC-1347 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
180487,3 | GOCBC-1347: Check if agent nil when logging TransactionATRLocation | master | gocbcore | Status: MERGED | +2 | +1 |