影響対象Azure Event Hubs の pub/sub または入力バインディング
You were affected if you consumed messages through the Azure Event Hubs pub/sub component or received events through the Azure Event Hubs input binding.
An event your application returned `RETRY` for, or one still in flight when the sidecar crashed or partition ownership was lost, was checkpointed and never redelivered, silently downgrading Dapr's documented at-least-once delivery guarantee ("Dapr attempts to redeliver the message until successful delivery") to at-most-once.
No error was surfaced to the publisher or subscriber when this happened.
Sibling pub/sub components such as Kafka and Service Bus already conditioned their commit or checkpoint on successful handling; only Event Hubs did not.
The Azure Event Hubs pub/sub and input binding components advanced (checkpointed) their Event Hubs offsets without regard to whether the application actually handled the event successfully.
`processEvents()` invoked the application through `handleAsync()`, but the error `handleAsync()` returned was discarded at the call site, leaving `UpdateCheckpoint()` with no condition to check before running.
Both delivery modes were affected, in different ways:
- With the default `enableInOrderMessageDelivery: false`, checkpointing happened fire-and-forget, independent of message delivery to the application.
- With `enableInOrderMessageDelivery: true`, the component waited for the handler to return before checkpointing, but checkpointed anyway when the handler responded `RETRY`.github.com/dapr/dapr/releases/tag/v1.17.15