===== base-20261114-084426 ===== PR 24007 | base | b2259d3c6ca71e59cea0c9cc0b9e8d8a90a027f9 Microsoft Windows Server 2025 Datacenter | Node v26.12.1; vp vp v1.6.0 Local vite-plus: vite-plus v1.4.0 Tools: vite v8.3.5 rolldown v1.2.15 vitest v5.0.5 oxfmt v0.74.0 oxlint v1.89.0 oxlint-tsgolint v7.0.2004 tsdown v0.23.1 Environment: Package manager pnpm v12.14.0 Node.js v26.12.1 (engines.node) Real HNS/WSL dynamic exclusions; no administered reservation Protocol tcp Port Exclusion Ranges Start Port End Port ---------- -------- 5357 5357 5985 5985 47001 47001 61001 61100 61101 61200 61201 61300 * - Administered port exclusions. Path hash bucket: 78; base port: 61078; head port: 20078 Bare Node listen ::1:61078 -> EACCES Bare Node listen 127.0.0.1:61078 -> EACCES > vp test run --project browser src/components/ChatMarkdown.browser.test.tsx --- complete command output --- note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead. System.Management.Automation.RemoteException ⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯ Error: listen EACCES: permission denied ::1:61078 at Server.setupListenHandle [as _listen2] (node:net:2368:21) at listenInCluster (node:net:2499:12) at GetAddrInfoReqWrap.callback (node:net:2728:7) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:134:8) { code: 'EACCES', errno: -4092, syscall: 'listen', address: '::1', port: 61078 } System.Management.Automation.RemoteException System.Management.Automation.RemoteException System.Management.Automation.RemoteException Command exit code: 1 ===== base-20261114-085045 ===== PR 24007 | base | b2259d3c6ca71e59cea0c9cc0b9e8d8a90a027f9 Microsoft Windows Server 2025 Datacenter | Node v26.12.1; vp vp v1.6.0 Local vite-plus: vite-plus v1.4.0 Tools: vite v8.3.5 rolldown v1.2.15 vitest v5.0.5 oxfmt v0.74.0 oxlint v1.89.0 oxlint-tsgolint v7.0.2004 tsdown v0.23.1 Environment: Package manager pnpm v12.14.0 Node.js v26.12.1 (engines.node) Real HNS/WSL dynamic exclusions; no administered reservation Protocol tcp Port Exclusion Ranges Start Port End Port ---------- -------- 5357 5357 5985 5985 47001 47001 61001 61100 61101 61200 61201 61300 * - Administered port exclusions. Path hash bucket: 78; base port: 61078; head port: 20078 Bare Node listen ::1:61078 -> EACCES Bare Node listen 127.0.0.1:61078 -> EACCES > vp test run --project browser src/components/ChatMarkdown.browser.test.tsx --- complete command output --- note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead. System.Management.Automation.RemoteException ⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯ Error: listen EACCES: permission denied ::1:61078 at Server.setupListenHandle [as _listen2] (node:net:2368:21) at listenInCluster (node:net:2499:12) at GetAddrInfoReqWrap.callback (node:net:2728:7) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:134:8) { code: 'EACCES', errno: -4092, syscall: 'listen', address: '::1', port: 61078 } System.Management.Automation.RemoteException System.Management.Automation.RemoteException System.Management.Automation.RemoteException Command exit code: 1 ===== head-20261114-084853 ===== PR 24007 | head | 503b274e1027e01599d90d62a6b21f291fb7dd2f Microsoft Windows Server 2025 Datacenter | Node v26.12.1; vp vp v1.6.0 Local vite-plus: vite-plus v1.4.0 Tools: vite v8.3.5 rolldown v1.2.15 vitest v5.0.5 oxfmt v0.74.0 oxlint v1.89.0 oxlint-tsgolint v7.0.2004 tsdown v0.23.1 Environment: Package manager pnpm v12.14.0 Node.js v26.12.1 (engines.node) Real HNS/WSL dynamic exclusions; no administered reservation Protocol tcp Port Exclusion Ranges Start Port End Port ---------- -------- 5357 5357 5985 5985 47001 47001 61001 61100 61101 61200 61201 61300 * - Administered port exclusions. Path hash bucket: 78; base port: 61078; head port: 20078 Bare Node listen ::1:61078 -> EACCES Bare Node listen 127.0.0.1:61078 -> EACCES > vp test run --project browser src/components/ChatMarkdown.browser.test.tsx --- complete command output --- note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead. RUN v5.0.5 /apps/web ⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯ System.Management.Automation.RemoteException Vitest caught 1 unhandled error during the test run. This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected. System.Management.Automation.RemoteException ⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯ Error: Failed to connect to the browser session "1a359a1b-db67-41e3-b0fa-bcbf87b98c9e" [browser (chromium)] within the timeout. ❯ Timeout._onTimeout ../../node_modules/.pnpm/vitest@5.0.5_@types+node@24_0fcdc40c762ea80328a810af15534d0c/node_modules/vitest/dist/chunks/cli-api.De07GUeT.js:5507:33 ❯ listOnTimeout node:internal/timers:685:17 ❯ process.processTimers node:internal/timers:618:7 System.Management.Automation.RemoteException ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Test Files (1) Tests no tests Errors 1 error Start at 08:48:56 Duration 60.04s System.Management.Automation.RemoteException close timed out after 10000ms Tests closed successfully but something prevents Vite server from exiting You can try to identify the cause by enabling "hanging-process" reporter. See https://vitest.dev/guide/reporters.html#hanging-process-reporter Command exit code: 1 ===== head-20261114-085112 ===== PR 24007 | head | 503b274e1027e01599d90d62a6b21f291fb7dd2f Microsoft Windows Server 2025 Datacenter | Node v26.12.1; vp vp v1.6.0 Local vite-plus: vite-plus v1.4.0 Tools: vite v8.3.5 rolldown v1.2.15 vitest v5.0.5 oxfmt v0.74.0 oxlint v1.89.0 oxlint-tsgolint v7.0.2004 tsdown v0.23.1 Environment: Package manager pnpm v12.14.0 Node.js v26.12.1 (engines.node) Real HNS/WSL dynamic exclusions; no administered reservation Protocol tcp Port Exclusion Ranges Start Port End Port ---------- -------- 5357 5357 5985 5985 47001 47001 61001 61100 61101 61200 61201 61300 * - Administered port exclusions. Path hash bucket: 78; base port: 61078; head port: 20078 Bare Node listen ::1:61078 -> EACCES Bare Node listen 127.0.0.1:61078 -> EACCES > vp test run --project browser src/components/ChatMarkdown.browser.test.tsx --- complete command output --- note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead. RUN v5.0.5 /apps/web stdout | unknown test [08:51:52.739] WARN (#40): Could not discover the primary environment. { error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:20078/.well-known/t3/environment.], } stdout | src/components/ChatMarkdown.browser.test.tsx > loads a host image through the page's own route when there is no environment [08:51:53.397] WARN (#91): Could not discover the primary environment. { error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:20078/.well-known/t3/environment.], } stdout | src/components/ChatMarkdown.browser.test.tsx > ChatMarkdown file chip tooltips > wraps a long path so its file name stays inside the tooltip [08:51:55.776] WARN (#40): Could not discover the primary environment. { error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:20078/.well-known/t3/environment.], } stdout | src/components/ChatMarkdown.browser.test.tsx [08:51:56.438] WARN (#91): Could not discover the primary environment. { error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:20078/.well-known/t3/environment.], } ❯ |browser (chromium)| src/components/ChatMarkdown.browser.test.tsx (28 tests | 1 failed) 3538ms ✓ keeps compact audio playback loaded across signed URL renewals 343ms ✓ keeps decimal markers in nested user lists while documents keep their counter styles 113ms ✓ shows unavailable audio when a workspace embed has no thread 40ms ✓ loads a host image through the page's own route when there is no environment 62ms ✓ loads the source for the current theme through the image route 34ms ✓ sizes a raw HTML image by width and height written with px units 37ms ✓ reuses the parse of a streaming reply's finished blocks when it remounts 32ms ✓ reuses the parse of a remounted message that has stable extra plugins 28ms ✓ highlights a code block's own source when an earlier block of the same length was cached 307ms ✓ ChatMarkdown favicon privacy (1) ✓ suppresses private link images while preserving public links across updates 34ms ✓ ChatMarkdown external link labels (1) ✓ keeps a leading emoji whole 14ms ✓ ChatMarkdown streaming (4) ✓ runs only a complete single-line shell block after a click 128ms ✓ edits the current task text and marker after reusing a renderer 48ms ✓ unchecks the remaining read-only task when the checked row above it is removed 24ms ✓ unchecks the remaining editable task when the checked row above it is removed 15ms ✓ ChatMarkdown workspace file opens (1) ✓ keeps a newer absolute file open when an earlier repo-relative lookup finishes 35ms ✓ ChatMarkdown skill chips (2) ✓ shows the skill's details and opens its instructions 646ms ✓ names a mentioned model as its provider does, without a thread 34ms ✓ ChatMarkdown headings (2) ✓ keeps insight streaming, reference links, and heading anchors in one message 62ms ✓ never gives two headings the same id, even when a suffix matches another heading 25ms ✓ ChatMarkdown inline code selection (2) ✓ selects the whole inline code span on double-click, but only a word in fenced code 226ms ✓ selects the whole line on triple-click beside a favicon link or a file chip 249ms ✓ ChatMarkdown alert copy (1) ✓ copies a fully selected callout as alert Markdown and a partial one as text 29ms ✓ ChatMarkdown file chip tooltips (1) ✓ wraps a long path so its file name stays inside the tooltip 872ms ✓ ChatMarkdown editor deep links (2) ✓ keeps local editor file links 22ms ✓ still drops other editor links and unknown schemes 18ms ❯ ChatMarkdown Windows file links (1) × still rejects unsafe schemes 39ms ✓ ChatMarkdown host media (1) ✓ explains a host video the connection cannot read instead of offering a retry 21ms System.Management.Automation.RemoteException ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯ System.Management.Automation.RemoteException FAIL |browser (chromium)| src/components/ChatMarkdown.browser.test.tsx > ChatMarkdown Windows file links > still rejects unsafe schemes AssertionError: expected '

unsafe and unknown alert(1)

" System.Management.Automation.RemoteException ❯ src/components/ChatMarkdown.browser.test.tsx:752:39 750| const { container } = screen; 751| expect(container.innerHTML).not.toContain("javascript:"); 752| expect(container.innerHTML).not.toContain("d:alert"); | ^ 753| expect(fileHrefs(container)).toEqual([]); 754| } ❯ node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-huvL6f-f.js?v=c6b5d12d:5237:20 System.Management.Automation.RemoteException ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ System.Management.Automation.RemoteException Test Files 1 failed (1) Tests 1 failed | 27 passed (28) Start at 08:51:15 Duration 40.55s (worker 72%, import 17%, tests 10%, setup 1%) Command exit code: 1 Observed live TCP listener: [::1]:20078; owner node.exe; head checkout=True