Because of the logic to exit Sentry CLI with a specific code, backtraces are not printed by default in Sentry CLI. This makes it harder to debug issues, since we don't always know where in code an error originates from. With RUST_BACKTRACE support, we can instruct users experiencing errors to set the environment variable.
Changes likely need to be made here:
Because of the logic to exit Sentry CLI with a specific code, backtraces are not printed by default in Sentry CLI. This makes it harder to debug issues, since we don't always know where in code an error originates from. With
RUST_BACKTRACEsupport, we can instruct users experiencing errors to set the environment variable.Changes likely need to be made here:
sentry-cli/src/commands/mod.rs
Line 352 in df403cd