-
Notifications
You must be signed in to change notification settings - Fork 217
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
Re-enable Babbage-era minimum UTxO calculation for the Babbage era #3388
Merged
iohk-bors
merged 10 commits into
master
from
jonathanknowles/babbage-minimum-utxo-corrections
Jul 18, 2022
Merged
Re-enable Babbage-era minimum UTxO calculation for the Babbage era #3388
iohk-bors
merged 10 commits into
master
from
jonathanknowles/babbage-minimum-utxo-corrections
Jul 18, 2022
Conversation
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
bors try |
jonathanknowles
changed the title
WIP: Babbage-era minimum UTxO corrections
WIP: Re-enable Babbage-era minimum UTxO calculation for the Babbage era
Jul 14, 2022
tryBuild failed: |
jonathanknowles
added
the
RESOLVING ISSUE
Mark a PR as resolving issues, for auto-generated CHANGELOG
label
Jul 14, 2022
jonathanknowles
force-pushed
the
jonathanknowles/babbage-minimum-utxo-corrections
branch
from
July 14, 2022 08:58
a5c2c5e
to
7936843
Compare
This appears to no longer be necessary, as the Cardano API now exports the `BabbageEra` identifier, and we no longer use any partial type signatures in this module.
jonathanknowles
force-pushed
the
jonathanknowles/babbage-minimum-utxo-corrections
branch
2 times, most recently
from
July 14, 2022 09:17
ddb596e
to
7baf98b
Compare
bors try |
tryBuild failed: |
bors try |
Note that these tests currently fail. Test failures are of the following form: ``` lib/shelley/test/unit/Cardano/Wallet/Shelley/MinimumUTxOSpec.hs:496:9: 1) computeMinimumCoinForUTxO, Golden Tests, goldenTests_computeMinimumCoinForUTxO Babbage, golden test #0 Falsified (after 1 test): resultExpected: Coin 995610 resultReturned: Coin 1077500 Condition violated: resultReturned == resultExpected To rerun use: --match "/computeMinimumCoinForUTxO/Golden Tests/goldenTests_computeMinimumCoinForUTxO Babbage/golden test #0/" ... ```
We re-introduce the Babbage-era minimum UTxO calculation in the Babbage era, and remove the workaround. This causes multiple integration tests to fail with `utxo_too_small`. For example: ```hs API Specifications, SHELLEY_TRANSACTIONS, TRANSMETA_ESTIMATE_01b - fee estimation includes no-schema metadata expected a successful response but got an error: ClientError (Object (fromList [("code",String "utxo_too_small"),("message",String "Some outputs have ada values that are too small. There's a minimum ada value specified by the protocol that each output must satisfy. I'll handle that minimum value myself when you do not explicitly specify an ada value for an output. Otherwise, you must specify enough ada. Here are the problematic outputs: - Expected min coin value: 1.077500 Address: 010d62b5...3a953592 Token bundle: coin: 0.999920 tokens: [] ")])) While verifying value: ( Status { statusCode = 403 , statusMessage = "Forbidden" } , Left ( ClientError ( Object ( fromList [ ( "code" , String "utxo_too_small" ) , ( "message" , String "Some outputs have ada values that are too small. There's a minimum ada value specified by the protocol that each output must satisfy. I'll handle that minimum value myself when you do not explicitly specify an ada value for an output. Otherwise, you must specify enough ada. Here are the problematic outputs: - Expected min coin value: 1.077500 Address: 010d62b5...3a953592 Token bundle: coin: 0.999920 tokens: [] " ) ] ) ) ) ) ```
jonathanknowles
force-pushed
the
jonathanknowles/babbage-minimum-utxo-corrections
branch
from
July 18, 2022 03:48
41aacaf
to
ea696fe
Compare
bors cancel |
bors try |
tryAlready running a review |
bors cancel |
bors try |
tryAlready running a review |
bors try- |
bors ping |
pong #expected |
bors try- |
bors try |
tryBuild failed: |
jonathanknowles
force-pushed
the
jonathanknowles/babbage-minimum-utxo-corrections
branch
from
July 18, 2022 05:12
ea696fe
to
5312321
Compare
bors try |
tryBuild failed: |
jonathanknowles
changed the title
WIP: Re-enable Babbage-era minimum UTxO calculation for the Babbage era
Re-enable Babbage-era minimum UTxO calculation for the Babbage era
Jul 18, 2022
Anviking
approved these changes
Jul 18, 2022
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.
🎉
bors r+ |
Build succeeded: |
iohk-bors
bot
deleted the
jonathanknowles/babbage-minimum-utxo-corrections
branch
July 18, 2022 10:14
WilliamKingNoel-Bot
pushed a commit
that referenced
this pull request
Jul 18, 2022
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue Number
ADP-2026
Summary
This PR reverts a subset of the changes made in #3318.
In particular, we:
In addition, we: