Messages stuck in sent state after creating invalid identity

Open annamcallister opened this issue 3 years ago • 1 comments

I added a new e2e test which created an invalid custom identity (using an already registered key and with a parent in a different org). The identity did not get created, but I did not get any events or messages that indicated that anything had gone wrong. All messages sent for creating the identity are stuck in sent state.

e.g. Screenshot 2022-08-10 at 17 54 19

Logs:

Aug 10 '22 17:08 annamcallister

Node 0 logged this:

[2022-08-10T16:23:09.884Z] ERROR Invalid message '64a395e6-8ccd-4ac5-97c7-f1550aee3e86'. Author 'did:firefly:custom_already_registered_1660148585_2' does not match identity registered to 0x4042810cbcb2587cf0fd27a06b5afca3a2c600f2: did:firefly:custom_already_registered_1660148585_1 (dd455e54-be36-4aeb-b2b1-b1b84859aaa4) dbtx=LCfZrmzi ns=default pid=1 role=aggregator

I think this should have triggered a message rejection, but didn't.

Aug 10 '22 18:08 awrichar