From 0128007ef13834de9ce50776f9b441e78dccf404 Mon Sep 17 00:00:00 2001 From: Wes Mason Date: Thu, 20 Aug 2026 00:04:24 +0100 Subject: [PATCH] docs(run-engine): cut the ck fair scheduling release note down to the change The note ran to three sentences, advertised a server env var a user cannot set, and described the pass-1 window degradation. .server-changes/README.md asks for a one-line description of behaviour rather than implementation, and says that needing a paragraph usually means you are describing the implementation. Reported by Devin on #4367; this is its suggested wording. --- .server-changes/2026-07-24-ck-fair-scheduling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.server-changes/2026-07-24-ck-fair-scheduling.md b/.server-changes/2026-07-24-ck-fair-scheduling.md index 0bd291c35..4b1cd3c83 100644 --- a/.server-changes/2026-07-24-ck-fair-scheduling.md +++ b/.server-changes/2026-07-24-ck-fair-scheduling.md @@ -3,4 +3,4 @@ area: webapp type: feature --- -The run queue can now serve concurrency keys fairly, so one key with a large backlog no longer starves runs waiting on other keys. It is opt-in and off by default. While a lot of keys on the same queue are all waiting on retry backoffs or future start times, ordering falls back to arrival order until they clear, so runs keep flowing but the fairness guarantee is relaxed for that period. +One concurrency key with a large backlog no longer holds up runs waiting on other keys on the same queue.