Skip to content
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

Various backports and alignments with polkadot-sdk (which does not depend on crates.io versions) #45

Conversation

bkontur
Copy link
Contributor

@bkontur bkontur commented Sep 27, 2023

Summary

This PR proposes several changes.

Explanation

A significant change of PR#1406 is the redefinition of what constitutes a "system" parachain. Previously, a "system" parachain was identified with para_id <= 1000. However, the PR#1406 changed a definition, considering a "system" parachain to have para_id <= 1999.

One consequence of this change is the reconsideration of the ChildSystemParachainAsSuperuser feature. This feature relies on the is_system function, which, in turn, depends on the para_id of a parachain to determine "system" status. However, further examination has revealed that there is no known scenario in which a system parachain would need to call the Kusama runtime with RuntimeOrigin::root() privileges. Consequently, maintaining the ChildSystemParachainAsSuperuser feature in the Kusama runtime is deemed unnecessary.

References

@bkontur bkontur mentioned this pull request Oct 19, 2023
@bkontur bkontur changed the title Remove ChildSystemParachainAsSuperuser from Kusama runtime + align "System" vs "common good" terminology Remove ChildSystemParachainAsSuperuser from Kusama runtime + align "System" vs "common good" terminology + other nits Nov 8, 2023
@bkontur bkontur changed the title Remove ChildSystemParachainAsSuperuser from Kusama runtime + align "System" vs "common good" terminology + other nits Various backports and alignments with polkadot-sdk (which does not depend on crates.io versions) Nov 17, 2023
@bkchr
Copy link
Contributor

bkchr commented Dec 7, 2023

/merge

@fellowship-merge-bot fellowship-merge-bot bot enabled auto-merge (squash) December 7, 2023 21:42
@fellowship-merge-bot
Copy link
Contributor

Enabled auto-merge in Pull Request

Available commands
  • /merge: Enables auto-merge for Pull Request
  • /merge cancel: Cancels auto-merge for Pull Request
  • /merge help: Shows this menu

For more information see the documentation

@acatangiu
Copy link
Contributor

review-bot is still not correctly working - it is not counting Rank 2 reviews although it says it does: https://github.com/polkadot-fellows/runtimes/pull/45/checks?check_run_id=19430490502

cc @Bullrich

@fellowship-merge-bot fellowship-merge-bot bot merged commit d67b905 into polkadot-fellows:main Dec 8, 2023
14 checks passed
@bkchr
Copy link
Contributor

bkchr commented Dec 8, 2023

review-bot is still not correctly working - it is not counting Rank 2 reviews although it says it does: https://github.com/polkadot-fellows/runtimes/pull/45/checks?check_run_id=19430490502

cc @Bullrich

Had you rerun the bot? I mean you got added probably to the fellowship after the bot ran the last time.

@bkontur bkontur deleted the bko-system-vs-common-good-nits branch January 8, 2024 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants