-
Notifications
You must be signed in to change notification settings - Fork 680
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
Reinitialize should allow to override existing config in collationGeneration #4833
Conversation
…eneration subsystem
IMO sounds better to me and reflects more what the name says. |
WIll change it to that then! thank you @bkchr |
Changed @bkchr |
@girazoki can you write a prdoc? |
sure |
prdoc/pr_4833.prdoc
Outdated
|
||
crates: | ||
- name: polkadot-node-collation-generation | ||
bump: none |
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.
Should be patch as the behaviour changes.
Co-authored-by: Andrei Sandu <[email protected]>
f8feebc
…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]>
Currently the
Initialize
andReinitialize
messages in the collationGeneration subsystem fail if:Initialize
if there exists already another configuration andReinitialize
if another configuration does not existI propose to instead change the behaviour of
Reinitialize
to always set the config regardless of whether one exists or not.