-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 2.2.5
-
Component/s: CLI Module, Telemetry Data
-
None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
1
-
Not Needed
-
Developer Tools
See https://github.com/mongodb-js/mongosh/pull/1955#issuecomment-2082303889 – a user rightfully points out that MONGOSH-1762 was an unintended breaking change in some scenarios because the enable/disable functions previously did not throw exceptions. We should wrap this in a try/catch and instead only print the error, if any, as a string (just like the regular return value currently)
- is caused by
-
MONGOSH-1762 monogsh says telemetry enabled despite forceDisableTelemetry set to true
- Closed
- is related to
-
MONGOSH-1141 Telemetry appears to the end user to be enabled even if forceDisableTelemetry is set to true
- Open