-
Notifications
You must be signed in to change notification settings - Fork 293
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
Port summonerd 63 changes to main #3497
Commits on Dec 8, 2023
-
Summonerd: add full pcli build instructions
(also center contribution text)
Configuration menu - View commit details
-
Copy full SHA for 9f2b5f8 - Browse repository at this point
Copy the full SHA 9f2b5f8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 18466e2 - Browse repository at this point
Copy the full SHA 18466e2View commit details -
Revert "Summonerd: tie view service failures to crash main service"
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.
Configuration menu - View commit details
-
Copy full SHA for cf01c83 - Browse repository at this point
Copy the full SHA cf01c83View commit details -
Restore css/html changes mixed into previous reverted commit.
The previous reverted commit also included unrelated HTML/CSS changes that presumably should be included.
Configuration menu - View commit details
-
Copy full SHA for 08204fe - Browse repository at this point
Copy the full SHA 08204feView commit details -
Configuration menu - View commit details
-
Copy full SHA for 256364d - Browse repository at this point
Copy the full SHA 256364dView commit details -
Configuration menu - View commit details
-
Copy full SHA for a2aa7f6 - Browse repository at this point
Copy the full SHA a2aa7f6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 44b349e - Browse repository at this point
Copy the full SHA 44b349eView commit details -
Configuration menu - View commit details
-
Copy full SHA for baee82e - Browse repository at this point
Copy the full SHA baee82eView commit details -
fix: foreign key error due to order of tables
phase1_contributions has a fk constraint to phase1_contribution_data so it needs to be populated first
Configuration menu - View commit details
-
Copy full SHA for 49c0f3c - Browse repository at this point
Copy the full SHA 49c0f3cView commit details -
the transition query will need to populate phase_2_contribution_data first in order for the FK constraint from phase2_contributions to be valid
Configuration menu - View commit details
-
Copy full SHA for 7ffafb3 - Browse repository at this point
Copy the full SHA 7ffafb3View commit details -
Configuration menu - View commit details
-
Copy full SHA for b2f614a - Browse repository at this point
Copy the full SHA b2f614aView commit details -
Summonerd: gracefully handle participant message channel closing
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.
Configuration menu - View commit details
-
Copy full SHA for 411c17d - Browse repository at this point
Copy the full SHA 411c17dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5239c05 - Browse repository at this point
Copy the full SHA 5239c05View commit details -
Configuration menu - View commit details
-
Copy full SHA for 67ccf41 - Browse repository at this point
Copy the full SHA 67ccf41View commit details -
summonerd: don't bail out on bad contribution data (#3434)
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.
Configuration menu - View commit details
-
Copy full SHA for 5c96fff - Browse repository at this point
Copy the full SHA 5c96fffView commit details -
Configuration menu - View commit details
-
Copy full SHA for a551193 - Browse repository at this point
Copy the full SHA a551193View commit details -
Configuration menu - View commit details
-
Copy full SHA for 88bba01 - Browse repository at this point
Copy the full SHA 88bba01View commit details