CekErrors inside the head are encoded

[nazrhom]

Hello, I noticed that when submitting a tx inside the head, the CekError that is attached to the TxInvalid event is encoded.

This is an example output I am getting:

{
  "tag": "TxInvalid",
  "validationError": {
    "reason": "ApplyTxError [UtxowFailure (WrappedShelleyEraFailure (UtxoFailure (UtxosFailure (ValidationTagMismatch (IsValid True) (FailedUnexpectedly [
    PlutusFailure \"\\nThe 3 arg plutus script (PlutusScript PlutusV1 ScriptHash 
      \\\"be2d605d3ff5fb351a2fe86551852ba7f34afe82187577957e3d7505\\\") fails.\\nCekError An error has occurred:  User 
      error:\\nThe provided Plutus code called 'error'.\\n
         The data is: {...}
         \"hZ8aA....AA==\"
  
    ,PlutusFailure \"\\nThe 3 arg plutus script (PlutusScript PlutusV1 ScriptHash 
       \\\"be2d605d3ff5fb351a2fe86551852ba7f34afe82187577957e3d7505\\\") fails.\\nCekError An error has occurred:  User 
      error:\\nThe provided Plutus code called 'error'.\\n
         The data is: {...} 
         \"hZ8aA.....AA==\"
    ]
   )))))]"
  },
  {...}
  }

where the hZ8aA....AA==\ strings can be decoded via debugPlutus to get a readable error.
I was wondering if it would be possible to show the decoded error directly in there. It looks like it is done in case of a single error https://github.com/input-output-hk/hydra-poc/blob/a1659dc856828811c54e722c4f8ac5bbfce2aab3/hydra-node/src/Hydra/Chain/Direct.hs#L555 but not in general, why is that the case?

[ghost]

The Direct module is the part that talks to the actual chain, whereas the Head maintains a completely separate Ledger and applies transactions on it independently, hence the discrepancy in error handling. It's perfectly reasonable to expect the off-chain ledger's errors to be reported in a more human-readable way :)