-
Notifications
You must be signed in to change notification settings - Fork 138
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 migration of storage path capabilities #3511
Merged
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
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit c945dc6 Collapsed results for better readability
|
invalid, because writes to other accounts
SupunS
approved these changes
Aug 8, 2024
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.
Description
#3503 added support for migrating capabilities with a
storage
path target.However, the implementation for it is invalid when it is run as an "account-based migration": The capability migration should only write to the account in which the capabilities are migrated, and no other accounts. However, the issuing of capability controllers might be for another account, i.e. writes to another account are performed.
Fix the migration by changing the approach:
Add a new value migration which does not actually migrate anything, but records all capability values with a
storage
domain targetAdd a new migration pass (in this PR only the function,
IssueAccountCapabilities
), which issues capability controllers for each account that is targeted by the previously detected capabilities. Writes are thus performed in the migrated account.Record the issued cap cons in the capability mapping, just like the link migration does.
The capability migration is reverted to just looking up capability IDs in the capability mapping, for any target domain.
master
branchFiles changed
in the Github PR explorer