From a170913202cf166b9a498c0393b753e794269a3a Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 30 Sep 2026 22:10:38 +0200 Subject: [PATCH] Issue 175: the link to issue 127 resolves --- .../00-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-ISSUES/175-an-announcement-behind-a-long-build-comes-back/00-report.md b/04-ISSUES/175-an-announcement-behind-a-long-build-comes-back/00-report.md index 6b8220b..a4ba169 100644 --- a/04-ISSUES/175-an-announcement-behind-a-long-build-comes-back/00-report.md +++ b/04-ISSUES/175-an-announcement-behind-a-long-build-comes-back/00-report.md @@ -26,7 +26,7 @@ The controller acts on what it consumes in **one loop, one message at a time**, builds every module the merge changed before it returns — minutes of work. The bus's acknowledgement window is thirty seconds. That contradiction was met once already: the message being worked on is kept alive by a heartbeat while its handler runs -([issue 127](../127-a-shared-delivery-subject-is-not-a-per-consumer-queue/00-report.md)'s stretch, +([issue 127](../127-a-module-event-derives-a-subject-nothing-publishes/00-report.md)'s stretch, controller PR 122). **The heartbeat covers one message.** The consumer is a push consumer with no bound on what it may have outstanding, so the client is handed everything that is waiting at once; the messages queued behind the one being built time out unacknowledged, come back after thirty seconds, -- 2.54.0