Skip to content

Cleanup UMP signal handling#12240

Open
eskimor wants to merge 1 commit into
ib-signed-scheduling-info-verifyfrom
rk-validate-block-cleanup
Open

Cleanup UMP signal handling#12240
eskimor wants to merge 1 commit into
ib-signed-scheduling-info-verifyfrom
rk-validate-block-cleanup

Conversation

@eskimor
Copy link
Copy Markdown
Member

@eskimor eskimor commented May 30, 2026

No description provided.

Make intent clear and correct.
@paritytech-workflow-stopper
Copy link
Copy Markdown

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/26677073962
Failed job name: test-linux-stable-int

Copy link
Copy Markdown
Contributor

@mchristou mchristou left a comment

Choose a reason for hiding this comment

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

Nice refactor of UMP signal handling!

Comment on lines +289 to +290
/// `peer_id` is a plain (non-`Option`) type, so the contract is "always override". Was not my
/// original idea (had optional override in mind), but it is fine either way.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This looks like a leftover

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Not really, but if I am the only one understanding it, we can remove the comment 🙈

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Feel free to merge, if that's the only nit and just remove the comment.

///
/// `peer_id` is a plain (non-`Option`) type, so the contract is "always override". Was not my
/// original idea (had optional override in mind), but it is fine either way.
pub fn from_resubmission(signed_info: &SignedSchedulingInfo) -> Self {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: from_scheduling_info is better IMO.

Comment on lines +50 to +53
/// Signed `claim_queue_offset` exceeds the runtime cap. The resubmission override takes the
/// offset from the signed payload, bypassing the in-block check `pallet_parachain_system`
/// applies to the block's own `CoreInfo` digest — so we re-apply the bound here, else a
/// resubmitter could sign an out-of-range offset.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: this is too verbose and talks about applying the bound, but this is just error variant definition.. I'd just say that this error is emitted when the scheduling proof offset override is larger than what runtime enforces as maximum.

if signals.select_core.replace((selector, offset)).is_some() {
panic!(
"Parachain emitted more than one `SelectCore` UMP signal; \
only the last block of a PoV may emit one"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We should remove "only the last block of a PoV may emit one" which make sense for block bundling, but this error is generic.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Not sure what you mean here.

@mchristou
Copy link
Copy Markdown
Contributor

@eskimor @sandreim
I will merge and address comments at base branch

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.

3 participants