Skip to content

test(e2e): give Claude a long-path config dir so the IDE server cannot abort - #718

Merged
stefanhoelzl merged 1 commit into
mainfrom
flaky-ide-server-crash
Sep 29, 2026
Merged

stefanhoelzl merged 1 commit into
mainfrom
flaky-ide-server-crash

Conversation

@stefanhoelzl

Copy link
Copy Markdown
Owner
  • e2e/agent-mock.ts: resolve the mock's CLAUDE_CONFIG_DIR with realpathSync.native, so a Windows runner's 8.3 short temp path (C:\Users\RUNNER~1\...) becomes its long form.
  • Root cause of the flaky agent-turn.e2e.ts failure on Windows ("No Claude session is running", e.g. runs 36478259567 and 36472837866): Claude installs the Claude Code extension into the IDE server mid-test; the extension watches CLAUDE_CONFIG_DIR from the server process, and libuv < 1.53.0 asserts (!_wcsnicmp(filename, dir, dirlen), fs-event.c:72) on the first event in a short-path watched directory (libuv#5010), aborting the whole server (exit 0xC0000409).
  • Reproduced deterministically on windows-2025 with node 24.18.1 / libuv 1.52.1 (VSCodium 1.135's node): fs.watch on the short path aborts, the realpathSync.native form works. No Node release bundles libuv 1.53.0 yet (deps: update libuv to 1.53.0 nodejs/node#66282 is open).

… abort

On Windows runners os.tmpdir() is an 8.3 short path (C:\Users\RUNNER~1\...).
The mock's CLAUDE_CONFIG_DIR inherited it, and the Claude extension, which
Claude installs into the IDE server mid-test, watches that folder from the
server process. libuv before 1.53.0 asserts on the first event in a
short-path watched directory (libuv#5010), so the whole IDE server aborted and
agent-turn failed with "No Claude session is running".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@stefanhoelzl stefanhoelzl added the internal no user facing changes label Sep 29, 2026
@stefanhoelzl
stefanhoelzl enabled auto-merge (rebase) September 29, 2026 15:47
@stefanhoelzl
stefanhoelzl merged commit e86a044 into main Sep 29, 2026
17 checks passed
@stefanhoelzl
stefanhoelzl deleted the flaky-ide-server-crash branch September 29, 2026 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal no user facing changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant