-
Notifications
You must be signed in to change notification settings - Fork 206
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
feat: make software upgrade coreProposals
conditional on upgrade plan name
#9575
Merged
Merged
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
95174a2
feat(builders): non-ambient `strictPriceFeedProposalBuilder` in `pric…
michaelfig 5cc190d
feat(app): establish mechanism for adding core proposals by `upgradeP…
michaelfig 52f02b7
fix(builders): use proper `oracleBrand` subkey case
michaelfig ddc072d
chore(cosmos): extract `app/upgrade.go`
michaelfig b3182a4
chore: fix error handling of upgrade vaults proposal
mhofman ea568a2
fix: retry upgrade vaults price quote
mhofman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason for waiting for a quote when upgrading
vaultFactory
? @mhofman @Chris-HibbertMy guess is that in
vaultDirector
'smakePriceLockWaker
;agoric-sdk/packages/inter-protocol/src/vaultFactory/vaultDirector.js
Lines 447 to 450 in ac88da5
allManagersDo
iterates over all vault managers to invoke theirlockOraclePrices
sequentially. If there's a case such as no price updates are pushed for a certain vault manager whenpriceLockWaker
is awake, thenlockOraclePrices
for that certain vault manager will fail. Which will result with vault managers added later than the failing one will not be able to lock their prices becauseallManagersDo
invokeslockOraclePrices
sequentially, see:agoric-sdk/packages/inter-protocol/src/vaultFactory/vaultDirector.js
Lines 267 to 273 in ac88da5
I have already opened an issue about this, please see #9706. In the issue I have a possible fix which worked for me quite nicely.
However, I am very curios to find out what other reasons there may be for waiting a price feed update before upgrading
vaultFactory
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we run the coreEval to do the upgrade, we'll be upgrading vaultFactory, and replacing auctions, as well as replacing all the priceAuthorities. After replacing the priceAuthorities, the oracle operators have to manually intervene in order to accept new invitations, and do some reconfiguration in order to start feeding information to the new priceAuthorities. I don't have any indication of whether that will take a half hour or a couple of days.
During the interim, it's best that the vaults and auctions continue to listen to the old priceAuthorities. The indication that the switchover is complete is that any price starts coming via the new priceAuthorities. At that point, we upgrade the vaultFactory, which will then start paying attention to the new priceAuthorities.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Chris!