[go: up one dir, main page]

Backport v22 !17279: Rollup node: use correct constant to identify active/lost outbox messages

Alain Mebsoutrequested to merge
alain@functori@backport_17279 into v22-release

Backport !17279 (merged) to v22: Rollup node: use correct constant to identify active/lost outbox messages

Commits

  • fd0b2f7e Rollup node: fetch max_active_outbox_levels from protocol constants
  • 2b696e7f Rollup node: use correct constant to identify active/lost outbox msgs
  • 2e0597df Doc: changelog for fix

Original MR description

What

The rollup node used the wrong constant to determine if an outbox message had passed its execution deadline and was lost. This MR fixes this behavior to use the correct constant.

Why

In the case where messages were not executed, they would be removed from the executable set too early and appeared as lost in the RPC /local/outbox/pending. A rollup node catching up on unexecuted outbox messages could miss their execution, incorrectly believing they exceeded their deadline. This last issue is less serious as rollup nodes execute outbox messages as soon as possible.

How

Fetching a new constant in the protocol plugin.

Merge request reports