GKaszewski/k-ap
1
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: delivery failure reporting for consumer-side DLQ #9

New Issue
Open
opened 2026-05-30 01:22:38 +00:00 by GKaszewski · 0 comments
GKaszewski commented 2026-05-30 01:22:38 +00:00
Owner
Copy Link

FederationEvent::DeliveryFailed already exists and is published when an EventPublisher is configured. However:

  • When no publisher is set (fire-and-forget mode), failures are only logged
  • There's no structured retry metadata (attempt count, last error, next retry time)
  • Consumers have no way to inspect or replay failed deliveries

The library should remain infra-agnostic — it shouldn't own a queue. But it should provide richer failure context so consumers can build their own DLQ/retry logic on top.

`FederationEvent::DeliveryFailed` already exists and is published when an `EventPublisher` is configured. However: - When no publisher is set (fire-and-forget mode), failures are only logged - There's no structured retry metadata (attempt count, last error, next retry time) - Consumers have no way to inspect or replay failed deliveries The library should remain infra-agnostic — it shouldn't own a queue. But it should provide richer failure context so consumers can build their own DLQ/retry logic on top.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GKaszewski
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GKaszewski/k-ap#9
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?