-
Notifications
You must be signed in to change notification settings - Fork 137
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
Improve errors in state migration #3154
Conversation
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit dc574a2 Collapsed results for better readability
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3154 +/- ##
=======================================
Coverage 80.54% 80.54%
=======================================
Files 381 381
Lines 92743 92764 +21
=======================================
+ Hits 74696 74717 +21
Misses 15337 15337
Partials 2710 2710
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@SupunS Thank you for the quick review! Changed my mind in the approach and extended this a bit. I think the new approach will be better, as it will allow us to debug thanks to the stack trace, but also it will not stop the whole migration just when a Go runtime error is encountered. |
a3de7d7
to
c64a00b
Compare
Work towards #3096
Description
Introduce a new error type,
MigrationError
, which captures migration location information.Include a stack trace when reporting it for recovered errors
master
branchFiles changed
in the Github PR explorer