From 3e061a6b41c2aabbca470e6692a9b4e43edf28e9 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Thu, 5 Nov 2026 23:43:07 +0000 Subject: [PATCH 1/2] chore(deps): update dependency @copilotkit/aimock to v1.47.0 --- apps/vscode-e2e/package.json | 2 +- pnpm-lock.yaml | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/apps/vscode-e2e/package.json b/apps/vscode-e2e/package.json index 187a130ab8..508b1f54f9 100644 --- a/apps/vscode-e2e/package.json +++ b/apps/vscode-e2e/package.json @@ -25,7 +25,7 @@ "@roo-code/config-eslint": "workspace:^", "@roo-code/config-typescript": "workspace:^", "@roo-code/types": "workspace:^", - "@copilotkit/aimock": "1.35.0", + "@copilotkit/aimock": "1.47.0", "@types/mocha": "10.0.10", "@types/node": "catalog:", "@types/vscode": "1.100.0", diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 0fb1d69415..2035d1d167 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -187,8 +187,8 @@ importers: apps/vscode-e2e: devDependencies: '@copilotkit/aimock': - specifier: 1.35.0 - version: 1.35.0(vitest@4.1.12) + specifier: 1.47.0 + version: 1.47.0(vitest@4.1.12) '@playwright/test': specifier: 1.64.1 version: 1.64.1 @@ -1527,8 +1527,8 @@ packages: '@chevrotain/types@11.1.2': resolution: {integrity: sha512-U+HFai5+zmJCkK86QsaJtoITlboZHBqrVketcO2ROv865xfCMSFpELQoz1GkX5GzME8pTa+3kbKrZHQtI0gdbw==} - '@copilotkit/aimock@1.35.0': - resolution: {integrity: sha512-dWtNUeaWD4jaC3Kv9oBiCoIczENM6u8pWBCmybn0/hSFEY57yqCtOGPsVNIG/YlmwbH8p5sgtL6xZzo1FnPi8g==} + '@copilotkit/aimock@1.47.0': + resolution: {integrity: sha512-wFPQ8olsToCnsEfJricsCizm9YFrrv/GJ77avB0YRsGP1r5hxvQ4SOl0ATUBa6aowSXkr3ENJaxWsndVXSZfkw==} engines: {node: '>=20.15.0'} hasBin: true peerDependencies: @@ -9968,7 +9968,7 @@ snapshots: '@chevrotain/types@11.1.2': {} - '@copilotkit/aimock@1.35.0(vitest@4.1.12)': + '@copilotkit/aimock@1.47.0(vitest@4.1.12)': optionalDependencies: vitest: 4.1.12(@opentelemetry/api@1.9.1)(@types/node@22.20.5)(@vitest/coverage-v8@4.1.12)(@vitest/ui@4.1.12)(jsdom@26.1.0)(vite@8.3.5(@types/node@22.20.5)(esbuild@0.28.2)(jiti@2.7.0)(tsx@4.23.15)(yaml@2.9.1)) From 5da6bd3b929420f13e784ec3e90e56b635dde2f4 Mon Sep 17 00:00:00 2001 From: Elliott de Launay Date: Sat, 7 Nov 2026 20:29:02 +0000 Subject: [PATCH 2/2] docs(e2e): update aimock client-disconnect comments --- apps/vscode-e2e/AGENTS.md | 12 +++++++----- apps/vscode-e2e/src/suite/subtasks.test.ts | 9 +++++---- 2 files changed, 12 insertions(+), 9 deletions(-) diff --git a/apps/vscode-e2e/AGENTS.md b/apps/vscode-e2e/AGENTS.md index 421194f766..a2ef44aff7 100644 --- a/apps/vscode-e2e/AGENTS.md +++ b/apps/vscode-e2e/AGENTS.md @@ -140,11 +140,13 @@ The `model` field can be added to either match when a test targets a specific mo Use `streamingProfile: { ttft: }` on a fixture, not a flat `latency: `, when a test needs to simulate a slow or hung provider (e.g. to cancel an in-flight request mid-stream). `ttft` delays only the first SSE chunk, so the pending window is exactly the configured value. Flat `latency` -delays _every_ chunk, and aimock never observes client disconnects — after a test cancels the -request, a flat-latency stream keeps flushing chunks server-side for `chunks × latency` before -reaching the dead socket, which can interleave with the next test's request against the same mock -server. See `SUBTASK_API_HANG_RESPONSE_LATENCY_MS` in `fixtures/subtasks.ts` for an example, -including the bounded post-test drain the calling suite uses to wait out that window. +delays _every_ chunk. Before aimock 1.47.0, the mock did not observe client disconnects — after a +test cancelled the request, a flat-latency stream kept flushing chunks server-side for +`chunks × latency` before reaching the dead socket, which could interleave with the next test's +request against the same mock server. Version 1.47.0 stops the reply on disconnect, but the +suite keeps its drain wait until an e2e run shows it is not needed. See +`SUBTASK_API_HANG_RESPONSE_LATENCY_MS` in `fixtures/subtasks.ts` for an example, including the +bounded post-test drain the calling suite uses to wait out that window. ## 404 errors in logs are expected diff --git a/apps/vscode-e2e/src/suite/subtasks.test.ts b/apps/vscode-e2e/src/suite/subtasks.test.ts index 857c8accc5..314f9c4b48 100644 --- a/apps/vscode-e2e/src/suite/subtasks.test.ts +++ b/apps/vscode-e2e/src/suite/subtasks.test.ts @@ -93,10 +93,11 @@ const waitForAimockRequestContaining = async ( // suite becomes flaky again on slow CI runners, widen this value first. const SUBTASK_API_HANG_DRAIN_GRACE_MS = 500 -// aimock does not observe client disconnects: after the API-hang child request is cancelled, -// the mock keeps the delayed stream pending server-side until the fixture's ttft has fully -// elapsed, then flushes the remaining chunks to the dead socket. A streamed request opened by -// the next test can interleave with that late flush, so wait out the remainder of the delayed +// aimock 1.47.0 stops and journals a reply when the client disconnects. Before that, the mock +// kept the delayed stream pending server-side until the fixture's ttft had fully elapsed, then +// flushed the remaining chunks to the dead socket. A streamed request opened by the next test +// could interleave with that late flush. This wait is a conservative guard kept until an e2e +// run shows it is not needed: wait out the remainder of the delayed // window before the next test runs. The deadline is anchored to the journal timestamp of the // request this test created (never earlier traffic), and bounded by one latency window plus // grace, so it cannot hide a genuine hang.