Fix local contract upgrade #20296
Open
Fix local contract upgrade #20296
+1,152
−225
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
paulbrauner-da
force-pushed
the
pb/fix-local-contracts
branch
from
934174c
to
c95b04e
Compare
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.
Fixes #20282.
We now always perform the upgrade validation check in the engine, so the
NeedUpgradeVerificationquestion is effecively unused. I'll remove it in a latter PR as it will require quite some cleanup.I've removed test cases that test impossible situations if we assume the upload and type checkers have run, and which now fail because we try to import values.
I added a bunch of daml-script tests as a sanity check, but I don't cover the entire space (disclosed contracts, fetch, fetch by interface, etc.). I plan to do that as part of the "one true test" so I don't want to replicate too much work here.