-
Notifications
You must be signed in to change notification settings - Fork 703
fix: early exit for top-level undefined errors #6448
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
fix: early exit for top-level undefined errors #6448
Conversation
Is this change in error types consensus-breaking? I think it would be good to add a convincing test that demonstrates that it is not consensus breaking. It should be possible to setup a test kind of like this one (https://github.com/stacks-network/stacks-core/blob/master/stackslib/src/chainstate/nakamoto/coordinator/tests.rs#L880) where instead of producing a contract which uses |
a8aa32b
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #6448 +/- ##
===========================================
+ Coverage 78.86% 79.33% +0.46%
===========================================
Files 558 558
Lines 343239 343329 +90
===========================================
+ Hits 270699 272372 +1673
+ Misses 72540 70957 -1583
... and 95 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This PR implements a fix for throwing the expected error (
UndefinedVariable
) instead of aCostError
when the contract contains a top-level variable that isn't defined.