-
Notifications
You must be signed in to change notification settings - Fork 207
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
priceQuery must return a quote #2831
Comments
This looks like a good actual example of a cross vat bug that can be tracked back to its origin using the extra tracking info added by ses 0.12.7. Did this turn out to be useful in practice? Is this sufficiently representative of other bugs we expect people to run into that it is a good expository example? |
fixes #2831 priceAggregator shows that when priceQuery() returns a falsy value, createQuote() is expected to return undefined. This happens when the comparefunction returns false, so the promise isn't resolved. I added a test of the priceAuthority in multipoolAutoSwap. The test fails before the change (The first trigger gets false on the comparison) and passes afterward.
The top of the stack and the error message showed me all the context I needed. I re-studied the model I had based the code on (priceAggregator) and figured out why the assertion was incorrect. #2839 is the fix. I think that means the answer to your question is mostly yes, but I didn't actually need the context, etiology or symptoms to figure out what was wrong. |
…2839) fixes #2831 priceAggregator shows that when priceQuery() returns a falsy value, createQuote() is expected to return undefined. This happens when the comparefunction returns false, so the promise isn't resolved. I added a test of the priceAuthority in multipoolAutoSwap. The test fails before the change (The first trigger gets false on the comparison) and passes afterward.
Describe the bug
To Reproduce
Occurs when creating a vault and then closing it immediately afterward. Trying to find the minimal steps to reproduce.
The text was updated successfully, but these errors were encountered: