fix contract calls into clarity2 contracts #711
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for #709 - check out that issue for more details and a repro of the bug.
This PR does two things:
costs-3boot contractstacks-blockchainand added it to various "default boot code" places, including in the project manifestcontract-call?inclarity-repl, I set the epoch to 2.1.The latter fix was the only thing that actually fixed the issue. The exact line of code is here: https://github.com/hstove/clarinet/blob/0ca1d66cb47e39763061a9017f7e45771938c896/components/clarity-repl/src/repl/session.rs#L593 . Without this line, my issue still fails.
One thing I noticed, via some debugging, was that my contract was being added to the Clarity DB with epoch "2.0" in tests, even though I have it specified as 2.1 in my Clarinet.toml. If that bug was fixed (which I haven't figured out), would that fix the bug as well?