Skip to content
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

fix: use permanent backoff when stacker set not found #5104

Merged
merged 9 commits into from
Sep 17, 2024

Conversation

hstove
Copy link
Contributor

@hstove hstove commented Aug 22, 2024

When the signer fetches the stacker set for a cycle, and the response is "not found" (because there isn't a PoX anchor block yet), a "permanent" error is returned instead of "transient". This will exit the exponential backoff function that would previously retry this request until the max timeout (5 seconds) was reached.

@hstove hstove requested a review from a team as a code owner August 22, 2024 13:47
@hstove hstove linked an issue Aug 22, 2024 that may be closed by this pull request
@jferrant
Copy link
Collaborator

Will this cause issues in the prepare phase though when it has not yet been calculated? I see that the "tests::signer::v0::reloads_signer_set_in" test is failing now.

@kantai kantai requested a review from a team as a code owner September 17, 2024 15:38
kantai
kantai previously approved these changes Sep 17, 2024
Copy link
Member

@kantai kantai left a comment

Choose a reason for hiding this comment

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

LGTM -- let's just make sure that the CI tests we expect to pass all pass

obycode
obycode previously approved these changes Sep 17, 2024
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

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

This makes sense to me. I think adding in the return might cause a clippy warning though.

stacks-signer/src/client/stacks_client.rs Outdated Show resolved Hide resolved
@kantai kantai dismissed stale reviews from obycode and themself via e8e7de1 September 17, 2024 17:44
@hstove
Copy link
Contributor Author

hstove commented Sep 17, 2024

LGTM! I can't review as it's my PR, but thank you @kantai for fixing this!

@kantai kantai added this pull request to the merge queue Sep 17, 2024
@kantai
Copy link
Member

kantai commented Sep 17, 2024

Marking as "merge when ready" -- the failing tests all pass locally. Two of these flaky tests (which are already flaky in develop) I think I have fixes for, so will open a PR to fix them soon.

Merged via the queue into develop with commit ddd3001 Sep 17, 2024
1 check passed
@blockstack-devops
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[signer] request for upcoming reward set can introduce 5s of delay
7 participants