From bc8d369d69659d042a24c0561369323b14f2e50d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81lvaro=20Tejero=20Cantero?= Date: Tue, 3 Nov 2026 15:17:15 +0100 Subject: [PATCH] :books: Say why the example climit config carries queues The comment on the branch limits said the header requires a queue on every entry. Nothing requires one at runtime: climit.clj::wrap skips a declared limit with no configuration and logs a warning. Only the test example-config-bounds-every-wait checks this file for a queue, and the numbers are example defaults, not measurements. AI-assisted-by: claude-opus-5-5 --- backend/resources/climit.edn | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/backend/resources/climit.edn b/backend/resources/climit.edn index 95487cb2a1..6ce07303a1 100644 --- a/backend/resources/climit.edn +++ b/backend/resources/climit.edn @@ -115,9 +115,10 @@ ;; `files_pull_request.clj::update-pull-request-snapshot`), which is ;; the anchor's shape again. ;; - ;; Every entry carries a queue, as the header requires: a command takes - ;; its own limits before the root ones, so an entry without a queue lets - ;; its waiters pile up without bound. The write-side global queues + ;; The numbers here are example defaults, not measurements. Every entry + ;; of this file carries a queue because `climit_test.clj` checks this + ;; file for one; at runtime a limit with no entry is skipped with a + ;; warning (`climit.clj::wrap`). The write-side global queues ;; follow the anchor's ratio of five waiters to three permits, rounded ;; up. The per-profile entry of one permit and a queue of two keeps a ;; single designer to one operation at a time. The two read-side