Log NATS ack/nak failures instead of discarding them #1924

Closed
opened 2026-11-12 16:35:17 +00:00 by sam · 1 comment
Owner

reactions.go discards 16 Ack/Nak results; spanrelay and the eventbus consumer do the same. A failed ack on a work queue means redelivery with no trace. Log every failure through the injected logger with context.

Done when no _ = msg.Ack/Nak/Term remains.

reactions.go discards 16 Ack/Nak results; spanrelay and the eventbus consumer do the same. A failed ack on a work queue means redelivery with no trace. Log every failure through the injected logger with context. Done when no `_ = msg.Ack/Nak/Term` remains.
sam added the chorelow labels 2026-11-12 16:35:17 +00:00
Author
Owner

Done in 68e8552f: reaction, span relay and event consumer ack/nak failures are logged. The one in the daemon's submitNATSTask goes with #1929. task check passed.

Done in 68e8552f: reaction, span relay and event consumer ack/nak failures are logged. The one in the daemon's submitNATSTask goes with #1929. task check passed.
sam closed this issue 2026-11-12 16:57:19 +00:00
sam added a new dependency 2026-11-13 02:50:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1924