Skip to content

e.input.format.acdc.bytes.f

Those bytes don't read as an ACDC I can verify.

Retrying the same thing changes nothing.

What a response says

I could not read an ACDC out of the bytes you handed me: {cause}.

The placeholders are filled from cause, which travel positionally in the args member of the response.

What to do

verify_acdc takes one ACDC in any serialization SerderACDC parses, genus-pinned or bare. Registry events and key events are different artifacts with different verbs.

Where it sits

Sorter e — Error. The problem clearly defeats someone's intentions.
Obstacle e.input. — What you sent
Disposition f — Final. Retrying the same thing changes nothing.

A handler can match this code exactly, or by any prefix above it: e.input., e.input.format., e.input.format.acdc., e.input.format.acdc.bytes..

Declared in heti.