novox/hq
3
0
Fork 0
Code Issues 5 Pull Requests 4 Releases Wiki Activity

Issue 175: the link to issue 127 resolves #235

Merged
jschoubben merged 1 commits from fix/issue-175-link into main 2026-09-30 20:10:41 +00:00
Conversation 0 Commits 1 Files Changed 1
+1 -1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
04-ISSUES/175-an-announcement-behind-a-long-build-comes-back/00-report.md
+1 -1
View File
@@ -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 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 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 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 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 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, messages queued behind the one being built time out unacknowledged, come back after thirty seconds,