You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, when BuildTxBodyErrorAutoBalance is raised, there is barely any information about what really happened. Especially when a validator error is raised.
Describe the solution you'd like
It'd be useful to return our balanced transaction (as selecting inputs and collateral can indeed influence script behavior) with the error.
Describe alternatives you've considered
N/A
Additional context
The addition is simple. Amend the BuildTxBodyErrorAutoBalance constructor to contain GYBalancedTx and amend attach this data type within makeTransactionBodyAutoBalanceWrapper. It should not prompt any API changes.
The text was updated successfully, but these errors were encountered:
I might have a better idea actually. I've been looking into the ledger and realized that I might be able to add the ability to retrieve the exact ScriptContext used with every plutus script in a transaction into CLB. Which means we can see it during validation failures in the "emulator log".
Is your feature request related to a problem? Please describe.
Currently, when
BuildTxBodyErrorAutoBalance
is raised, there is barely any information about what really happened. Especially when a validator error is raised.Describe the solution you'd like
It'd be useful to return our balanced transaction (as selecting inputs and collateral can indeed influence script behavior) with the error.
Describe alternatives you've considered
N/A
Additional context
The addition is simple. Amend the
BuildTxBodyErrorAutoBalance
constructor to containGYBalancedTx
and amend attach this data type withinmakeTransactionBodyAutoBalanceWrapper
. It should not prompt any API changes.The text was updated successfully, but these errors were encountered: