-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Stop using package:stack_trace and Chain.capture #8803
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
Conversation
|
Looks like this fails on Windows |
|
@goderbauer PTAL at the Windows specific fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/cc @yjbanov who had occasion to change this code to work this way just last week.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, n/m -- he didn't add the Chain.capture(), and this is still semantically the same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a slight semantic difference here -- previously, it would use the value of traceStartup that was passed to its constructor if it was unspecified in run(). Now it'll always default to false
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
|
LGTM with 1 comment |
- [x] Don't use package:stack_trace. - [x] Don't use Chain.capture. - [x] Fix an instance of aggressive catching of exceptions Related #8742
yjbanov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also remove the dependency in pubspec.yaml?
|
+1 to this patch |
Related #8742
@tvolkert