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

Reinitialize should allow to override existing config in collationGeneration #4833

Merged

Conversation

girazoki
Copy link
Contributor

@girazoki girazoki commented Jun 19, 2024

Currently the Initialize and Reinitialize messages in the collationGeneration subsystem fail if:

  • Initialize if there exists already another configuration and
  • Reinitialize if another configuration does not exist

I propose to instead change the behaviour of Reinitialize to always set the config regardless of whether one exists or not.

@bkchr
Copy link
Member

bkchr commented Jun 21, 2024

We could also instead change the behaviour of Reinitialize to always set the config regardless of whether one exists or not.

IMO sounds better to me and reflects more what the name says.

@girazoki
Copy link
Contributor Author

WIll change it to that then! thank you @bkchr

@girazoki girazoki changed the title SetConfig and ClearConfig to allow for higher customization in collationGeneration subsystem Reinitialize should allow to override existing config in collationGeneration Jun 21, 2024
@girazoki
Copy link
Contributor Author

Changed @bkchr

@bkchr bkchr requested a review from skunert June 21, 2024 13:37
@bkchr bkchr added R0-silent Changes should not be mentioned in any release notes T0-node This PR/Issue is related to the topic “node”. and removed R0-silent Changes should not be mentioned in any release notes labels Jun 21, 2024
@bkchr
Copy link
Member

bkchr commented Jun 21, 2024

@girazoki can you write a prdoc?

@girazoki
Copy link
Contributor Author

@girazoki can you write a prdoc?

sure


crates:
- name: polkadot-node-collation-generation
bump: none
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be patch as the behaviour changes.

prdoc/pr_4833.prdoc Outdated Show resolved Hide resolved
Co-authored-by: Andrei Sandu <[email protected]>
prdoc/pr_4833.prdoc Outdated Show resolved Hide resolved
@bkchr bkchr enabled auto-merge June 23, 2024 09:11
@bkchr bkchr added this pull request to the merge queue Jun 23, 2024
Merged via the queue into paritytech:master with commit f8feebc Jun 23, 2024
142 of 158 checks passed
TarekkMA pushed a commit to moonbeam-foundation/polkadot-sdk that referenced this pull request Aug 2, 2024
…eration (paritytech#4833)

Currently the `Initialize` and `Reinitialize` messages in the
collationGeneration subsystem fail if:
-  `Initialize` if there exists already another configuration and
- `Reinitialize` if another configuration does not exist

I propose to instead change the behaviour of `Reinitialize` to always
set the config regardless of whether one exists or not.

---------

Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Andrei Sandu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T0-node This PR/Issue is related to the topic “node”.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants