-
Notifications
You must be signed in to change notification settings - Fork 97
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
Keep im-online
events decodable after pallet removal
#235
Keep im-online
events decodable after pallet removal
#235
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.
Looks sensible to me, assuming it was tested to actually work. (E.g. does the pallet path matter?)
Yes, I reproduced the problem in a local synthetic test and made sure it was resolved with this patch. Paths do not matter, TypeInfo only includes names, I'm not sure it's even critical in this case, but I still named the thing |
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.
This is a reasonable workaround. I assume we can safely remove this mock pallet after the runtime upgrade is applied (let's create an issue to not forget)?
/merge |
Enabled Available commands
For more information see the documentation |
64c9e16
into
polkadot-fellows:main
Fair enough, raised #242 |
Thank you! Good approach! |
This is a follow-up to #178, which aims to keep the
im-online
pallet events decodable after the pallet itself is removed.As discussed, the inability to decode events may result in missing a candidate in approval voting and a parachain finality stall. Although the circumstances of such an event are unlikely, it's better to safeguard them.
The transient code introduced in this PR should be removed after the upgrade is enacted.