mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-08-26 17:13:32 +00:00
d7d793c5bf
* feat(serve): make sub-session concurrency caps configurable The per-caller (5) and workspace-total (20) ceilings on concurrent create_sub_session sub-sessions were hardcoded, and 5 was too tight for legitimate parallel fan-out. Both are now configurable via serve.maxConcurrentSubSessionsPerCaller and serve.maxConcurrentSubSessionsTotal, with defaults raised to 16 and 24. The total default stays below the bridge's default maxSessions (32): finished sub-sessions linger in the session table until idle-reaped, so a total cap at the table limit would fail the next fan-out wave at bridge admission and starve interactive sessions of slots. Caps are a daemon-resource control, read from trust-filtered merged settings at launcher creation (primary, secondary, and dynamic workspaces); only positive integers are honored, anything else falls back to the built-in defaults. * fix(serve): clarify total-cap comment describes the default, not an invariant (#8341) * test(serve): pin sub-session cap schema defaults to runtime constants (#8341) * fix(serve): remove redundant optional chaining on non-optional parameter (#8341) * fix(serve): clamp total sub-session cap to tracked-id set size (#8341) The configurable maxConcurrentSubSessionsTotal could exceed MAX_TRACKED_SPAWNED_SESSIONS (1024), causing the depth-1 nesting gate's FIFO eviction to discard still-alive sub-session ids and break the single-level nesting guarantee. * fix(serve): surface sub-session cap fallbacks and schema ceiling (#8341) --------- Co-authored-by: qwen-code-ci-bot <qwen-code-ci-bot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| acp-bridge | ||
| audio-capture | ||
| channels | ||
| chrome-extension | ||
| cli | ||
| core | ||
| cua-driver | ||
| desktop | ||
| desktop-shell | ||
| mobile-mcp | ||
| sdk-java | ||
| sdk-python | ||
| sdk-typescript | ||
| vscode-ide-companion | ||
| web-shell | ||
| web-templates | ||
| webui | ||
| zed-extension | ||