-
Notifications
You must be signed in to change notification settings - Fork 293
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
Disallow truncated data in toplevel containers #921
Conversation
f71b993
to
ebc6635
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #921 +/- ##
==========================================
- Coverage 95.15% 95.08% -0.07%
==========================================
Files 140 138 -2
Lines 15785 15771 -14
==========================================
- Hits 15020 14996 -24
- Misses 765 775 +10
Flags with carried forward coverage won't be shown. Click here to find out more.
|
ebc6635
to
3812727
Compare
3812727
to
c65a79f
Compare
This needs updating tests in ethereum/tests cc @hugo-dc |
Disallow truncated data section in toplevel containers. This is now only allowed in some subcontainers. Co-authored-by: Paweł Bylica <pawel@ethereum.org>
The check is now part of validation of toplevel container. For creation transaction this is still required to be checked before validation to find out container/input data split.
c65a79f
to
d813e73
Compare
This change only affects what is allowed in tests. Truncated data sections are not allowed at top level now, to check truncated data rules, tests should put it into subcontainers.