-
Notifications
You must be signed in to change notification settings - Fork 214
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
make decodeTx not so strict when policy key is missing #3194
Conversation
I've run e2e suite against this PR -> https://github.com/input-output-hk/cardano-wallet/runs/5646577836?check_suite_focus=true Most of the tests are now passing (i.e. the fix addresses some of the failures), but not all of them. The remaining failures are:
Plutus:
These are Plutus scripts that actually mint some tokens and they fail with the same error:
Construct mint tx:
|
fe066fa
to
860a27c
Compare
@piotr-iohk plutus scripts now should pass. construct tx should not proceed when policy key is missing. I will add a way to set this key (via endpoint as it is not possible to do it with db migrations) in next PR. |
Executed e2e suite against this branch after changes again.
All is passing now: https://github.com/input-output-hk/cardano-wallet/actions/runs/2028501957 Note: Construct mint tx would still fail (there is no such test in e2e suite yet.), but I understand that's a topic for another PR. |
bors r+ |
3194: make decodeTx not so strict when policy key is missing r=paweljakubas a=paweljakubas adp-1549 <!-- Detail in a few bullet points the work accomplished in this PR. Before you submit, don't forget to: * Make sure the GitHub PR fields are correct: ✓ Set a good Title for your PR. ✓ Assign yourself to the PR. ✓ Assign one or more reviewer(s). ✓ Link to a Jira issue, and/or other GitHub issues or PRs. ✓ In the PR description delete any empty sections and all text commented in <!--, so that this text does not appear in merge commit messages. * Don't waste reviewers' time: ✓ If it's a draft, select the Create Draft PR option. ✓ Self-review your changes to make sure nothing unexpected slipped through. * Try to make your intent clear: ✓ Write a good Description that explains what this PR is meant to do. ✓ Jira will detect and link to this PR once created, but you can also link this PR in the description of the corresponding Jira ticket. ✓ Highlight what Testing you have done. ✓ Acknowledge any changes required to the Documentation. --> - [x] I have make sure checking for policy key is only taking place when minting/burning is on. ### Comments <!-- Additional comments, links, or screenshots to attach, if any. --> ### Issue Number <!-- Reference the Jira/GitHub issue that this PR relates to, and which requirements it tackles. Note: Jira issues of the form ADP- will be auto-linked. --> Co-authored-by: Pawel Jakubas <[email protected]>
Build failed:
|
bors retry |
3194: make decodeTx not so strict when policy key is missing r=paweljakubas a=paweljakubas adp-1549 <!-- Detail in a few bullet points the work accomplished in this PR. Before you submit, don't forget to: * Make sure the GitHub PR fields are correct: ✓ Set a good Title for your PR. ✓ Assign yourself to the PR. ✓ Assign one or more reviewer(s). ✓ Link to a Jira issue, and/or other GitHub issues or PRs. ✓ In the PR description delete any empty sections and all text commented in <!--, so that this text does not appear in merge commit messages. * Don't waste reviewers' time: ✓ If it's a draft, select the Create Draft PR option. ✓ Self-review your changes to make sure nothing unexpected slipped through. * Try to make your intent clear: ✓ Write a good Description that explains what this PR is meant to do. ✓ Jira will detect and link to this PR once created, but you can also link this PR in the description of the corresponding Jira ticket. ✓ Highlight what Testing you have done. ✓ Acknowledge any changes required to the Documentation. --> - [x] I have make sure checking for policy key is only taking place when minting/burning is on. ### Comments <!-- Additional comments, links, or screenshots to attach, if any. --> ### Issue Number <!-- Reference the Jira/GitHub issue that this PR relates to, and which requirements it tackles. Note: Jira issues of the form ADP- will be auto-linked. --> Co-authored-by: Pawel Jakubas <[email protected]>
Build failed:
|
bors r+ |
Build succeeded: |
adp-1549
Comments
Issue Number