Render consistent plutus script failure output #4659
Draft
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
Jimbo4350
force-pushed
the
jordan/implement-consistent-script-failure-output
branch
from
41422fb to
5de4fd9
Compare
Jimbo4350
force-pushed
the
jordan/implement-consistent-script-failure-output
branch
from
5de4fd9 to
208311d
Compare
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.
This PR reconciles the differences between the error output in the event of a plutus script failure from:
cardano-cli transaction buildcardano-cli transaction submitNB: This is blocked until we bump to the next ledger release. Once this happens,
ValidationFailed{V1,V2}will havePlutusDebugin it's constructor (which we need).Example output: