-
Notifications
You must be signed in to change notification settings - Fork 180
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
Update stable cadence feature branch #5290
Update stable cadence feature branch #5290
Conversation
This change replaces hash-based validation of Cadence values in order to prepare for atree inlining to be incorporated into the migration program. Also added validate flag to enable validation during migration since enabling validation can increase duration of migration.
Added flag --log-verbose-validation-error to enable logging of entire Cadence values on validation error during atree migration.
This is a temporary (and inefficient) workaround to check number of fields in Cadence CompositeValue. In the future, CompositeValue.FieldCount() will be added to Cadence, so that function can be used to improve this workaround.
…e-value-validation Replace hash-based validation of migrated Cadence values to use `Equal()`
# Conflicts: # fvm/evm/types/events.go
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## feature/stable-cadence #5290 +/- ##
==========================================================
- Coverage 55.62% 49.85% -5.78%
==========================================================
Files 995 190 -805
Lines 95196 17043 -78153
==========================================================
- Hits 52954 8497 -44457
+ Misses 38264 7955 -30309
+ Partials 3978 591 -3387
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
👏 👏
Lots of unit tests are still failing, because the new required Burner contract isn't getting deployed during bootstrapping. @joshuahannan once we know if it's integrated or not, I can add it (or not) |
#5285 + #5289 by @SupunS and @joshuahannan + some more updates and fixes.
Uses onflow/flow-emulator#552 for integration tests