Skip to content

fix: Check slash round lifetime when looking back executable rounds#17652

Merged
PhilWindle merged 1 commit intonextfrom
palla/check-lifetime-in-slash-lookback
Oct 13, 2025
Merged

fix: Check slash round lifetime when looking back executable rounds#17652
PhilWindle merged 1 commit intonextfrom
palla/check-lifetime-in-slash-lookback

Conversation

@spalladino
Copy link
Contributor

In #17245 we changed the slasher client to check for older rounds pending execution, with a config variable that indicates how far to look back.

However, the lifetime in rounds in staging ended up being smaller than the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.

In #17245 we changed the slasher client to check for older rounds
pending execution, with a config variable that indicates how far to look
back.

However, the lifetime in rounds in staging ended up being smaller than
the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.
@PhilWindle PhilWindle enabled auto-merge October 13, 2025 11:19
@PhilWindle PhilWindle added this pull request to the merge queue Oct 13, 2025
Merged via the queue into next with commit 04c2923 Oct 13, 2025
20 of 21 checks passed
@PhilWindle PhilWindle deleted the palla/check-lifetime-in-slash-lookback branch October 13, 2025 12:17
@AztecBot
Copy link
Collaborator

❌ Failed to cherry-pick to v2 due to conflicts. Please backport manually.

spalladino pushed a commit that referenced this pull request Oct 16, 2025
…17652)

In #17245 we changed the slasher client to check for older rounds
pending execution, with a config variable that indicates how far to look
back.

However, the lifetime in rounds in staging ended up being smaller than
the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.
spalladino pushed a commit that referenced this pull request Oct 16, 2025
…17652)

In #17245 we changed the slasher client to check for older rounds
pending execution, with a config variable that indicates how far to look
back.

However, the lifetime in rounds in staging ended up being smaller than
the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.
spalladino pushed a commit that referenced this pull request Oct 16, 2025
…17652)

In #17245 we changed the slasher client to check for older rounds
pending execution, with a config variable that indicates how far to look
back.

However, the lifetime in rounds in staging ended up being smaller than
the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.
spalladino pushed a commit that referenced this pull request Oct 17, 2025
…17652)

In #17245 we changed the slasher client to check for older rounds
pending execution, with a config variable that indicates how far to look
back.

However, the lifetime in rounds in staging ended up being smaller than
the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.
spalladino pushed a commit that referenced this pull request Oct 17, 2025
…17652)

In #17245 we changed the slasher client to check for older rounds
pending execution, with a config variable that indicates how far to look
back.

However, the lifetime in rounds in staging ended up being smaller than
the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.
spalladino added a commit that referenced this pull request Oct 17, 2025
…17652) (#17749)

Backport of #17652

In #17245 we changed the slasher client to check for older rounds
pending execution, with a config variable that indicates how far to look
back.

However, the lifetime in rounds in staging ended up being smaller than
the lookback, so we were picking rounds no longer valid.

This PR checks that we do not look that far back.

Co-authored-by: PhilWindle <60546371+PhilWindle@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants