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

Port summonerd 63 changes to main #3497

Merged
merged 17 commits into from
Dec 8, 2023

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented Dec 8, 2023

Closes #3446. This PR rebases summonerd-feature-branch on top of current main. A single commit was excluded due to conflicts: that from #3291. We definitely want a plan for handling the split-brain, so we can either 1) separately apply that commit, resolving conflicts manually; or 2) configure summonerd to use a single, non-LB grpc endpoint on 64. In the interest of time, I suggest option 2.

I'm also open to squashing this down into a single commit, but up to you, @cronokirby.

cronokirby and others added 16 commits December 8, 2023 09:52
(also center contribution text)
This reverts commit bb795bd.

The `wait_for_crash` method doesn't work correctly and will generate new
crashes while waiting to check if the view service crashed.  We need to use the
code we actually did the dry run with.  As per this morning's discussion,
making the view service more robust is something we should work in, but it's
something that requires design work and code review and should not be dropped
only into the summonerd service without testing.
The previous reverted commit also included unrelated HTML/CSS changes that
presumably should be included.
phase1_contributions has a fk constraint to phase1_contribution_data
so it needs to be populated first
the transition query will need to populate phase_2_contribution_data
first in order for the FK constraint from phase2_contributions
to be valid
Basically, we should treat this as a rare but expected thing, and blame
and strike the participant for this, rather than bring down the server
as if it were an unexpected failure.
The better code pattern for this would be to blanket-handle errors in the method, but at the moment it seems better to just fix the current issue.
Bumps the recommended version of pcli to v0.63.3, to match the latest
point release [0]. Also removes the `cargo run` invocations to match
the recent change to the docs, to recommend installing binaries over
compiling from source [1].

[0] #3469
[1] #3442
Copy link
Contributor

@cronokirby cronokirby left a comment

Choose a reason for hiding this comment

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

This looks good to me. I agree with option 2 of using a non-load balanced endpoint being a good idea.

@conorsch conorsch merged commit 88fb275 into main Dec 8, 2023
5 checks passed
@conorsch conorsch deleted the 3446-port-summonerd-63-changes-to-main-via-rebase branch December 8, 2023 21:07
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.

Backport summonerd fixes for Testnet 64
4 participants