Closed philipgiuliani closed 1 year ago
NOTE: this was solved by a workaround in #14
Deleting a stream causes a system event to be sent to the persistent subscription to the $ce-prefix
projection.
This is unexpected since persistent subscriptions are created with the exclude_system_events
filter.
Also, adding the filter to the catch-up subscription in the EventPublishers
causes no events to be received.
When performing a hard-delete of a stream, the adapter will receive a system event which cannot be handled.
Steps to reproduce:
curl -i -X DELETE "http://127.0.0.1:2113/streams/prefix-stream_name" -H "ES-HardDelete:true"
Expected result: Stream gets deleted and applications works fine
Actual result: Application terminates with the following crash:
The JSON deserializer will be called with the following arguments: