From da01ea105cf91a56fd0e088aa96d8da500f82506 Mon Sep 17 00:00:00 2001 From: Jakub Zych Date: Wed, 23 Sep 2026 21:15:43 +0200 Subject: [PATCH] docs(08-05): record fetchguard flake resolution in deferred items --- .../08-oauth2-1-authorization-server/deferred-items.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.planning/phases/08-oauth2-1-authorization-server/deferred-items.md b/.planning/phases/08-oauth2-1-authorization-server/deferred-items.md index 005c76e..1fe65d1 100644 --- a/.planning/phases/08-oauth2-1-authorization-server/deferred-items.md +++ b/.planning/phases/08-oauth2-1-authorization-server/deferred-items.md @@ -60,3 +60,9 @@ run; passes on every isolated run (`-count=5`) and every package-level run (`-count=3`). Last touched in Phase 6 (`e50e2dd`); no Phase 8 plan modifies `fetchguard`. Timing-sensitive streaming assertion under load. Not a Phase 8 regression; left for a later hardening pass. + +**Resolution (orchestrator, after 08-05):** the flake tripped the post-wave +gate on two of three full runs, so it was fixed in `summercms.go` commit +`test(fetchguard): widen streaming-cap ceiling to stop flake under parallel +runs`. The ceiling moved from 64 KiB to 1 MiB; the assertion still proves the +client does not buffer an unbounded body (the handler would reach 8 MiB).