-
Notifications
You must be signed in to change notification settings - Fork 212
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
auctioneer doesn't recover when collateral is added without a price #8296
Comments
oops... the log excerpt above was from ollinet |
Diagnosis: auction schedule endTime is pastThis seems somewhat by-design, as a result of #7775:
ps shows Impact: auctions for all collaterals affected by a problem with 1context: devnet proposal 2
...
...
|
treatment: update auction params (not yet effective)It had the desired effect to some extent:
but then immediately:
vat id info from
|
Here's the log transcript of the auctioneer on the last auction round:
from 16:00:10 to 16:24:13, we see the previous complete round of the auction. There are 8 steps ( That round was the first time the stATOM book appeared, and it immediately complained that it didn't have a price. 43 minutes later, the auctioneer gets a price update for stATOM, but by then it's too late. I think what happened is that the auctionBook threw an exception while performing a task for Separately, the current code has no way to recover if |
@otoole-brendan you don't need auctions running on devnet any time soon, right? I think the next steps to that are tracked elsewhere: |
Describe the bug
While testing changing oracle prices for ATOM and stATOM with Simply Staking on Devnet in order to test liquidation - I noticed that when checking inter auction status that the auction hadn't ran since 8/23:
red herring from ollinet logs
Per Dan:
logs show
which translates to...
so it could be that under the covers, all is well, but vstorage isn't getting updated somehow.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Auction should continue to run
The text was updated successfully, but these errors were encountered: