-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing log_level
causes premature exit
#30
Comments
Thanks for reporting @vsomayaji |
Maybe we should change to:
I'm not entirely sure if |
@kamilogorek Do you know if |
Yes, purposefully, but its a subject to change in v2 - getsentry/sentry-cli#1130
Yes, exit codes are valid way to determine if something succeeded |
Thanks, so I guess the suggested change makes sense. |
Environment
Sentry SaaS with
sentry_dart_plugin
1.0.0-beta.1
.Steps to Reproduce
log_level
todebug
inpubspec.yaml
.flutter packages pub run sentry_dart_plugin
.Expected Result
Source maps are uploaded.
Actual Result
After creating the release, the CLI exits prematurely because debug statements like this are written to STDERR:
This appears to be because this code exits whenever STDERR is not empty:
sentry-dart-plugin/lib/src/utils/log.dart
Lines 111 to 113 in 347089e
The text was updated successfully, but these errors were encountered: