mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-11-07 06:19:43 -10:00
27a4485db5
* test(integration): disable managed auto-memory by default in E2E harnesses (#13009) Co-authored-by: Qwen-Coder <[email protected]> * test(integration): tie E2E memory defaults to the settings schema Type both harnesses' managed-memory defaults with `satisfies Settings['memory']` so a key rename fails typecheck:integration instead of silently re-enabling the extractor, and merge per-suite memory overrides per key so opting back into one flag keeps its sibling off. Co-authored-by: Qwen-Coder <[email protected]> * test(integration): dedupe E2E memory defaults and pin their literal values --------- Co-authored-by: Qwen-Coder <[email protected]> Co-authored-by: 易良 <[email protected]> Co-authored-by: qwen-code-dev-bot <[email protected]>
21 lines
855 B
TypeScript
21 lines
855 B
TypeScript
/**
|
|
* @license
|
|
* Copyright 2026 Qwen Team
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
import type { Settings } from '../packages/cli/src/config/settings.js';
|
|
|
|
// Since #12913 the managed-memory extractor fires a forked-agent model
|
|
// request on every tool-completing turn and the headless CLI awaits it before
|
|
// exit — dead latency and extra endpoint load for runs that never assert
|
|
// memory behavior. Suites that need it opt back in per key via
|
|
// options.settings. The `satisfies` tie to the settings schema turns a key
|
|
// rename into a typecheck:integration failure instead of silently
|
|
// re-enabling the extractor. Both harnesses share this single definition so
|
|
// their defaults cannot drift apart.
|
|
export const E2E_MEMORY_SETTINGS_DEFAULTS = {
|
|
enableManagedAutoMemory: false,
|
|
enableManagedAutoDream: false,
|
|
} satisfies Settings['memory'];
|