-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fix nostd build of several crates #4060
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
fc2869f
Remove wrong nostd
ggwpez 15a6851
Zepter: make nostd-deps optional
ggwpez dd6b1a5
Always enable scale feature
ggwpez c2e04c4
Always enable pallet-state-trie-migration
ggwpez db09175
Remove optional: these pallets are not optional at all
ggwpez a17f95e
Add use sp_std::vec stuff
ggwpez b18244a
Fix benchmarking crate
ggwpez 58c424d
Fix docs
ggwpez 8155936
add prdoc
ggwpez dddf1b0
Fix feature gates
ggwpez 0ee158e
Fix feature gate
ggwpez 430868e
Fix imports
ggwpez 1578135
Also fix crates FRAME and frame-try-runtime
ggwpez 4b8a29c
Fix more
ggwpez 06e8c43
Revert uapi feature changes
ggwpez a1cc2b1
Merge branch 'master' into oty-fix-nostd
ggwpez 83f5967
Use alloc instead of sp-std
ggwpez cecb8f4
ah-rococo: Enable V1 state trie migration
ggwpez c70875c
Revert changes to FRAME crate
ggwpez 0d32f27
FRAME crate: larger experimental warning
ggwpez 54552f3
Merge remote-tracking branch 'origin/master' into oty-fix-nostd
ggwpez 3d764a5
Merge remote-tracking branch 'origin/master' into oty-fix-nostd
ggwpez 3a2f964
Fix features
ggwpez File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh now I remembre, this is used for multiple network so the feature was needed to have one running V0 while another one was already migrated (likely westend/rococo a long time ago).
Sounds ok to remove it so migration got started everywhere. One point I am not sure is related to the account use as controller: currently it is hardcoded to :
probably would need a different one per network, this is not really convenient.
Worst case, what can happen with this chain is some parachain moving to hybrid mode (both v0 and v1 in tree, if warpsync is not use by the parachain this should not be an issue) and not being able to migrate because no account to process the typescript driven migration.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay thanks for the context. For Rococo it is probably fine, as it will be decommissioned soon anyway.
Just going to leave it as is, and hope that DevOps has the keys. Otherwise we do another upgrade or root call etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I confirm we have the key to
0x8458ed39dc4b6f6c7255f7bc42be50c2967db126357c999d44e12ca7ac80dc52to be able to process the migration.