mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
66662d4a88
PR #4718 added the LGP D5 coverage wave, taking langgraph-python's declared D5 feature set to ~28. With FEATURE_CONCURRENCY=2 that's 14 features per worker × ~15s realistic wall-clock = ~210s — over the prior 3-min cap before any slack. Post-merge cycles confirmed the math: 17 langgraph-python features ran cleanly and flipped green, but the remaining ~10 hit `errorClass: "abort"` with `errorDesc: "aborted"`, the abort-cascade signature where the global cap fires before the per-feature loop reaches them. Per-feature timeout (5min) bounds wedged features but doesn't bound the slug's total feature count against the outer cap. Bump to 10 min — gives ~5x headroom at current feature count. Lighter integrations (5–10 features, ~60s) still exit early without sitting on the cap, so cycle wall-clock barely changes (cron stays every 15 min, concurrency=4 hides the slow integration's tail behind the others). Revisit `FEATURE_CONCURRENCY` before raising further — Chromium context count scales with it and the Railway pod's 2.4GB headroom budget assumes the current value. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>