
=== 01-prime-seven ===
$ vp test run --project browser src/components/ComposerPromptEditorTiptap.citationDraft.browser.test.tsx src/components/chat/ComposerModelEffort.browser.test.tsx src/components/files/PdfViewer.browser.test.tsx src/components/pullRequest/PullRequestSummaryTab.browser.test.tsx src/components/settings/AddProviderInstanceDialog.environment.browser.test.tsx src/components/Sidebar.browser.test.tsx src/components/files/AttachmentFilePreview.browser.test.tsx
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 <checkout>/apps/web


 Test Files  7 passed (7)
      Tests  114 passed (114)
   Start at  11:15:43
   Duration  44.98s (import 49%, tests 27%, worker 22%, setup 2%)

EXIT CODE: 0
OPTIMIZER IMPORTS: {"node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/_metadata.json": ["@pierre/diffs/ssr"]}

=== 02-restore-nine ===
$ vp test run --project browser src/components/ComposerPromptEditorTiptap.citationDraft.browser.test.tsx src/components/chat/ComposerModelEffort.browser.test.tsx src/components/files/PdfViewer.browser.test.tsx src/components/pullRequest/PullRequestSummaryTab.browser.test.tsx src/components/settings/AddProviderInstanceDialog.environment.browser.test.tsx src/components/Sidebar.browser.test.tsx src/components/files/AttachmentFilePreview.browser.test.tsx src/connection/storage.browser.test.ts src/components/settings/TypographySettings.browser.test.tsx
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 <checkout>/apps/web

11:16:57 AM [vite] (client) dependencies optimized: @effect/vitest, effect/testing
11:16:57 AM [vite] (client) optimized dependencies changed. reloading

[vitest] Vite unexpectedly reloaded a test. This may cause tests to fail, lead to flaky behaviour or duplicated test runs.
For a stable experience, add the newly optimized dependencies to your config's `optimizeDeps.include` field manually.

 ❯ |browser (chromium)| src/connection/storage.browser.test.ts (0 test)
 ❯ |browser (chromium)| src/components/settings/TypographySettings.browser.test.tsx (0 test)
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > bounded binary previews > reauthorizes a failed image when retry is clicked
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > bounded binary previews > reauthorizes a failed image when retry is clicked
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > bounded binary previews > reauthorizes a failed image when retry is clicked
An error occurred in the <PreviewImageContent> component.

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://react.dev/link/error-boundaries to learn more about error boundaries.

stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > large text preview recovery > retains the workspace viewer across URL renewals and reloads revisions and manual refreshes
[11:17:06.259] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > large text preview recovery > retains the workspace viewer across URL renewals and reloads revisions and manual refreshes
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > large text preview recovery > retains the workspace viewer across URL renewals and reloads revisions and manual refreshes
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
An error occurred in the <MermaidViewer> component.

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://react.dev/link/error-boundaries to learn more about error boundaries.

stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
[11:17:09.278] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
[11:17:12.295] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
[11:17:15.311] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
[11:17:18.330] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "im\u0067": "/pixel.png" }
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "im\u0067": "/pixel.png" }
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ label: &key img, *key: '/pixel.png' }
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ label: &key img, *key: '/pixel.png' }
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A["<img src=//attacker.invalid/pixel.png>"]
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A["<img src=//attacker.invalid/pixel.png>"]
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <--> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <--> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <==> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <==> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <-.-> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <-.-> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the --> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the --> arrow
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > reloads a workspace Word file after a preview remount
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > reloads a workspace Word file after a preview remount
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > reloads a workspace Word file after a preview remount
An error occurred in the <OfficeViewer> component.

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://react.dev/link/error-boundaries to learn more about error boundaries.

stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > reloads a workspace Word file after a preview remount
[11:17:21.334] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > reloads a workspace Word file after a preview remount
[11:17:24.338] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > reloads a workspace Word file after a preview remount
[11:17:27.341] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > clears an Office metadata error when the same URL becomes previewable
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > clears an Office metadata error when the same URL becomes previewable
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
An error occurred in the <FontFilePreview> component.

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://react.dev/link/error-boundaries to learn more about error boundaries.

stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
[11:17:33.384] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
[11:17:36.403] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
[11:17:39.419] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
[11:17:42.438] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > toggles a Mermaid attachment between diagram and source through the lazy preview
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > toggles a Mermaid attachment between diagram and source through the lazy preview
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > toggles a Mermaid attachment between diagram and source through the lazy preview
An error occurred in the <MermaidViewer> component.

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://react.dev/link/error-boundaries to learn more about error boundaries.

stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > keeps a workspace PDF open across URL renewals and reloads it when the file changes
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > keeps a workspace PDF open across URL renewals and reloads it when the file changes
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > loads an edited HTML file outside the workspace from a renewed URL
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > loads an edited HTML file outside the workspace from a renewed URL
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > keeps an unchanged workspace HTML page loaded across commands and renews its grant
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > keeps an unchanged workspace HTML page loaded across commands and renews its grant
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > keeps a workspace PDF's page, offset and zoom when a new revision reloads it
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > keeps a workspace PDF's page, offset and zoom when a new revision reloads it
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > mounts a bounded set of saved notebook outputs as the reader scrolls
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > mounts a bounded set of saved notebook outputs as the reader scrolls
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > preserves rtf document text through the worker and attachment viewer
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > preserves rtf document text through the worker and attachment viewer
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stdout | src/components/files/AttachmentFilePreview.browser.test.tsx > preserves epub document text through the worker and attachment viewer
[11:17:45.456] WARN (#40): Could not discover the primary environment. {
  error: [ConnectionTransientError: Remote environment endpoint returned an invalid response from http://localhost:23531/.well-known/t3/environment.],
}
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > preserves epub document text through the worker and attachment viewer
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > preserves epub document text through the worker and attachment viewer
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > preserves ods document text through the worker and attachment viewer
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
stderr | src/components/files/AttachmentFilePreview.browser.test.tsx > preserves ods document text through the worker and attachment viewer
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.
 ❯ |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx (81 tests | 26 failed) 51193ms
   ❯ bounded binary previews (9)
     × preserves length-delimited local and global PAX attributes 326ms
     × shows generated SQLite columns and retains picker focus at 320 px 40ms
     × shows generated SQLite columns and retains picker focus at 1280 px 71ms
     × reauthorizes a failed image when retry is clicked 1048ms
   ❯ large text preview recovery (16)
     × retains the workspace viewer across URL renewals and reloads revisions and manual refreshes 739ms
   ❯ standalone Mermaid previews (8)
     × rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" } 10018ms
     × rejects resource syntax before Mermaid lays out A@{ "im\u0067": "/pixel.png" } 13ms
     × rejects resource syntax before Mermaid lays out A@{ label: &key img, *key: '/pixel.png' } 34ms
     × rejects resource syntax before Mermaid lays out A["<img src=//attacker.invalid/pixel.png>"] 19ms
     × renders the <--> arrow 16ms
     × renders the <==> arrow 15ms
     × renders the <-.-> arrow 18ms
     × renders the --> arrow 19ms
   × reloads a workspace Word file after a preview remount 10024ms
   × clears an Office metadata error when the same URL becomes previewable 22ms
   × reauthorizes and retries a failed sqlite attachment 17ms
   × loads a font attachment through the lazy preview 10054ms
   × toggles a Mermaid attachment between diagram and source through the lazy preview 1018ms
   × keeps a workspace PDF open across URL renewals and reloads it when the file changes 28ms
   × loads an edited HTML file outside the workspace from a renewed URL 30ms
   × keeps an unchanged workspace HTML page loaded across commands and renews its grant 39ms
   × keeps a workspace PDF's page, offset and zoom when a new revision reloads it 31ms
   × mounts a bounded set of saved notebook outputs as the reader scrolls 24ms
   × preserves rtf document text through the worker and attachment viewer 268ms
   × preserves epub document text through the worker and attachment viewer 334ms
   × preserves ods document text through the worker and attachment viewer 265ms

⎯⎯⎯⎯⎯⎯ Failed Suites 2 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  |browser (chromium)| src/connection/storage.browser.test.ts [ src/connection/storage.browser.test.ts ]
Error: Failed to import test file <checkout>/apps/web/src/connection/storage.browser.test.ts
 ❯ node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=c248c29a:5847:5
 ❯ collectTests node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=c248c29a:5823:3
 ❯ startTests node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=c248c29a:6511:17

Caused by: TypeError: Cannot read properties of undefined (reading 'config')
 ❯ initSuite node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=07d3f0c9:5181:23
 ❯ createSuiteCollector node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=07d3f0c9:5076:2
 ❯ Object.suiteFn node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=07d3f0c9:5259:10
 ❯ chain node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=07d3f0c9:4336:14
 ❯ src/connection/storage.browser.test.ts:11:1

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/28]⎯

 FAIL  |browser (chromium)| src/components/settings/TypographySettings.browser.test.tsx [ src/components/settings/TypographySettings.browser.test.tsx ]
Error: Failed to import test file <checkout>/apps/web/src/components/settings/TypographySettings.browser.test.tsx
 ❯ node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=c248c29a:5847:5
 ❯ collectTests node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=c248c29a:5823:3
 ❯ startTests node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/plugins.DPQHVT0p-nFBxamFO.js?v=c248c29a:6511:17

Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:23531/node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_jsx-dev-runtime.js?v=c248c29a
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/28]⎯


⎯⎯⎯⎯⎯⎯ Failed Tests 26 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > bounded binary previews > preserves length-delimited local and global PAX attributes
{
  isTrusted: true,
  type: 'error',
  target: {
    onmessage: null,
    postMessage: 'Function<postMessage>',
    terminate: 'Function<terminate>',
    constructor: 'Function<Worker>',
    onerror: null,
    addEventListener: 'Function<addEventListener>',
    dispatchEvent: 'Function<dispatchEvent>',
    removeEventListener: 'Function<removeEventListener>',
    when: 'Function<when>'
  },
  currentTarget: {
    onmessage: null,
    postMessage: 'Function<postMessage>',
    terminate: 'Function<terminate>',
    constructor: 'Function<Worker>',
    onerror: null,
    addEventListener: 'Function<addEventListener>',
    dispatchEvent: 'Function<dispatchEvent>',
    removeEventListener: 'Function<removeEventListener>',
    when: 'Function<when>'
  },
  eventPhase: 2,
  bubbles: false,
  cancelable: true,
  defaultPrevented: false,
  composed: false,
  timeStamp: 22787.300000000047,
  srcElement: {
    onmessage: null,
    postMessage: 'Function<postMessage>',
    terminate: 'Function<terminate>',
    constructor: 'Function<Worker>',
    onerror: null,
    addEventListener: 'Function<addEventListener>',
    dispatchEvent: 'Function<dispatchEvent>',
    removeEventListener: 'Function<removeEventListener>',
    when: 'Function<when>'
  },
  returnValue: true,
  cancelBubble: false,
  NONE: 0,
  CAPTURING_PHASE: 1,
  AT_TARGET: 2,
  BUBBLING_PHASE: 3,
  composedPath: 'Function<composedPath>',
  initEvent: 'Function<initEvent>',
  preventDefault: 'Function<preventDefault>',
  stopImmediatePropagation: 'Function<stopImmediatePropagation>',
  stopPropagation: 'Function<stopPropagation>',
  constructor: 'Function<Event>',
  stacks: []
}
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > bounded binary previews > shows generated SQLite columns and retains picker focus at 320 px
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > bounded binary previews > shows generated SQLite columns and retains picker focus at 1280 px
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > reauthorizes and retries a failed sqlite attachment
TypeError: Failed to fetch dynamically imported module: http://localhost:23531/node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/sql__js.js?v=c248c29a
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > bounded binary previews > reauthorizes a failed image when retry is clicked
AssertionError: the given combination of arguments (undefined and string) is invalid for this assertion. You can use an array, a map, an object, a set, a string, or a weakset instead of a string
 ❯ Proxy.<anonymous> node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:1916:15
 ❯ Proxy.<anonymous> node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:1786:14
 ❯ src/components/files/AttachmentFilePreview.browser.test.tsx:441:99
 ❯ checkCallback node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:5427:20

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > large text preview recovery > retains the workspace viewer across URL renewals and reloads revisions and manual refreshes
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ WorkspaceLargeTextPreview src/components/files/FilePreviewPanel.tsx:2907:12
    2088|     </>
    2089|   );
    2090| }
       |  ^
    2091|
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16739:20
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }
AssertionError: the given combination of arguments (undefined and string) is invalid for this assertion. You can use an array, a map, an object, a set, a string, or a weakset instead of a string
 ❯ Proxy.<anonymous> node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:1916:15
 ❯ Proxy.<anonymous> node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:1786:14
 ❯ vi.waitFor.timeout src/components/files/AttachmentFilePreview.browser.test.tsx:1239:99
 ❯ checkCallback node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:5427:20

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[7/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ "im\u0067": "/pixel.png" }
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A@{ label: &key img, *key: '/pixel.png' }
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > rejects resource syntax before Mermaid lays out A["<img src=//attacker.invalid/pixel.png>"]
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <--> arrow
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <==> arrow
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the <-.-> arrow
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > standalone Mermaid previews > renders the --> arrow
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ MermaidViewer src/components/files/MermaidViewer.tsx:9:12
      7| export default function MermaidViewer(props: { readonly text: string }…
      8|   const gt = useGT();
      9|   const [expanded, setExpanded] = useState<string | null>(null);
       |            ^
     10|   // Mermaid lays out DOM before sanitizing its SVG. Refuse resource a…
     11|   // syntax before that pass so standalone files cannot initiate reque…
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16715:529
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[8/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > reloads a workspace Word file after a preview remount
AssertionError: expected '' to contain 'Original outlook'

- Expected
+ Received

- Original outlook

 ❯ vi.waitFor.timeout src/components/files/AttachmentFilePreview.browser.test.tsx:1299:63
 ❯ checkCallback node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:5427:20

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[9/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > clears an Office metadata error when the same URL becomes previewable
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > mounts a bounded set of saved notebook outputs as the reader scrolls
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > preserves rtf document text through the worker and attachment viewer
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > preserves epub document text through the worker and attachment viewer
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > preserves ods document text through the worker and attachment viewer
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ OfficeViewer src/components/files/OfficeViewer.tsx:41:12
     40|   let size = 0;
     41|   try {
     42|     while (true) {
       |    ^
     43|       const { value, done } = await reader.read();
     44|       if (done) break;
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16715:529
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[10/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > loads a font attachment through the lazy preview
AssertionError: expected undefined to be 'Carlito.ttf' // Object.is equality

- Expected:
"Carlito.ttf"

+ Received:
undefined

 ❯ vi.waitFor.timeout src/components/files/AttachmentFilePreview.browser.test.tsx:1818:25
 ❯ checkCallback node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:5427:20

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[11/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > toggles a Mermaid attachment between diagram and source through the lazy preview
AssertionError: expected null not to be null
 ❯ src/components/files/AttachmentFilePreview.browser.test.tsx:1844:105
 ❯ checkCallback node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/index.aTZaPVhf-cSHNzfEV.js?v=c248c29a:5427:20

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[12/28]⎯

 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > keeps a workspace PDF open across URL renewals and reloads it when the file changes
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > loads an edited HTML file outside the workspace from a renewed URL
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > keeps an unchanged workspace HTML page loaded across commands and renews its grant
 FAIL  |browser (chromium)| src/components/files/AttachmentFilePreview.browser.test.tsx > keeps a workspace PDF's page, offset and zoom when a new revision reloads it
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ WorkspaceBrowserPreview src/components/files/FilePreviewPanel.tsx:249:12
    247|
    248| const HTML_PREVIEW_RENEW_BEFORE_EXPIRY_MS = 2 * 60_000;
    249| // Grants last an hour. A client clock far from the server's would oth…
       |            ^
    250| const HTML_PREVIEW_MIN_GRANT_HOLD_MS = 3 * 60_000;
    251| const HTML_PREVIEW_MAX_GRANT_HOLD_MS = 60 * 60_000;
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16739:20
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[13/28]⎯

⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯

Vitest caught 5 unhandled errors during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ PreviewImageContent src/components/files/PreviewImageContent.tsx:12:12
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16715:529
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

This error originated in "src/components/files/AttachmentFilePreview.browser.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The last test to run before this error was "reauthorizes a failed image when retry is clicked". This means either:
- the error was thrown while Vitest was running this test, or
- the error was thrown after the test completed, and this was the most recent test at that point.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ MermaidViewer src/components/files/MermaidViewer.tsx:9:12
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16715:529
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

This error originated in "src/components/files/AttachmentFilePreview.browser.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The last test to run before this error was "rejects resource syntax before Mermaid lays out A@{ "img": "//attacker.invalid/pixel.png" }". This means either:
- the error was thrown while Vitest was running this test, or
- the error was thrown after the test completed, and this was the most recent test at that point.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ OfficeViewer src/components/files/OfficeViewer.tsx:41:12
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16715:529
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

This error originated in "src/components/files/AttachmentFilePreview.browser.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The last test to run before this error was "reloads a workspace Word file after a preview remount". This means either:
- the error was thrown while Vitest was running this test, or
- the error was thrown after the test completed, and this was the most recent test at that point.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ FontFilePreview src/components/files/FontFilePreview.tsx:8:12
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16715:529
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

This error originated in "src/components/files/AttachmentFilePreview.browser.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The last test to run before this error was "loads a font attachment through the lazy preview". This means either:
- the error was thrown while Vitest was running this test, or
- the error was thrown after the test completed, and this was the most recent test at that point.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Cannot read properties of null (reading 'useMemoCache')
 ❯ exports.c node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/react_compiler-runtime.js?v=07d3f0c9:35:22
 ❯ MermaidViewer src/components/files/MermaidViewer.tsx:9:12
 ❯ Object.react_stack_bottom_frame node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:24490:12
 ❯ renderWithHooks node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:14748:19
 ❯ updateFunctionComponent node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16123:16
 ❯ beginWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:16715:529
 ❯ runWithFiberInDEV node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:11292:66
 ❯ performUnitOfWork node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19496:92
 ❯ workLoopSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19392:37
 ❯ renderRootSync node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/client-D0NYT3aK.js?v=c248c29a:19376:6

This error originated in "src/components/files/AttachmentFilePreview.browser.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The last test to run before this error was "toggles a Mermaid attachment between diagram and source through the lazy preview". This means either:
- the error was thrown while Vitest was running this test, or
- the error was thrown after the test completed, and this was the most recent test at that point.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯


 Test Files  3 failed | 6 passed (9)
      Tests  26 failed | 88 passed (114)
     Errors  5 errors
   Start at  11:16:30
   Duration  78.31s (import 42%, tests 30%, worker 27%, setup 1%)

EXIT CODE: 1
OPTIMIZER IMPORTS: {"node_modules/.vite/vitest/ef98362b8a6b0c8cd804b0d227aa1ffeaba89786/deps/_metadata.json": ["@effect/vitest", "@pierre/diffs/ssr", "effect/testing"]}

=== 03-warm-control-nine ===
$ vp test run --project browser src/components/ComposerPromptEditorTiptap.citationDraft.browser.test.tsx src/components/chat/ComposerModelEffort.browser.test.tsx src/components/files/PdfViewer.browser.test.tsx src/components/pullRequest/PullRequestSummaryTab.browser.test.tsx src/components/settings/AddProviderInstanceDialog.environment.browser.test.tsx src/components/Sidebar.browser.test.tsx src/components/files/AttachmentFilePreview.browser.test.tsx src/connection/storage.browser.test.ts src/components/settings/TypographySettings.browser.test.tsx
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 <checkout>/apps/web


 Test Files  9 passed (9)
      Tests  118 passed (118)
   Start at  11:17:50
   Duration  40.25s (import 47%, worker 28%, tests 24%, setup 1%)

EXIT CODE: 0
