-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Scheduler: remove empty agenda on cancel #12989
Conversation
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.
It seems like the original author intended to be like this, but seeing the data I also agree that we better not have all of these empty agendas.
I don't think we need a migration, the existing agendas would eventually be cleared up when they are in the past, right?
Yes, looks same to me. |
|
Only extended the condition with |
Signed-off-by: Oliver Tale-Yazdi <[email protected]>
But the current block is |
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.
Looks good, but CI needs to pass still.
Signed-off-by: Oliver Tale-Yazdi <[email protected]>
Signed-off-by: Oliver Tale-Yazdi <[email protected]>
Bot merge |
This pull request has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/polkadot-release-analysis-v0-9-37/1736/1 |
* Scheduler: remove empty agenda on cancel * use iter any * fix benches * remove trailing None * Add CleanupAgendas migration Signed-off-by: Oliver Tale-Yazdi <[email protected]> * fix ci Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Count non-empty agendas in migration Signed-off-by: Oliver Tale-Yazdi <[email protected]> Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: Oliver Tale-Yazdi <[email protected]>
* Scheduler: remove empty agenda on cancel * use iter any * fix benches * remove trailing None * Add CleanupAgendas migration Signed-off-by: Oliver Tale-Yazdi <[email protected]> * fix ci Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Count non-empty agendas in migration Signed-off-by: Oliver Tale-Yazdi <[email protected]> Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: Oliver Tale-Yazdi <[email protected]>
Fixes #12977 #12851
With the small change to the script provided by @ggwpez, you can see there are only agendas for the future blocks with all None items.
Its possible because we do not remove such agendas on a cancelation, and they get removed when serviced.
From the implementation and tests it looks like it was expected to have empty future agendas, nevertheless it seems to me valid, to remove them on the cancelations and address the raised issues.
// DONE fix benches
// DONE migration to remove empty agendas