github/penpot
1
0
Fork 0
mirror of https://github.com/penpot/penpot.git synced 2026-11-04 09:00:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

📚 Say why the example climit config carries queues

Browse Source 
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
This commit is contained in:
Álvaro Tejero Cantero 2026-11-03 15:17:15 +01:00
parent 30274b5320
commit bc8d369d69
No known key found for this signature in database
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
backend/resources/climit.edn
View File

@ -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