Skip to content

prep for most text formats #13

prep for most text formats

prep for most text formats #13

Triggered via push May 9, 2024 18:06
Status Failure
Total duration 3m 16s
Artifacts

test.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Unhandled error: src/models/attachment.ts#L24
TypeError: window.api.file.extractText is not a function ❯ Attachment.extractText src/models/attachment.ts:24:37 ❯ new Attachment src/models/attachment.ts:19:12 ❯ onAttach src/components/Prompt.vue:109:31 ❯ callWithErrorHandling node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:195:19 ❯ Object.callWithAsyncErrorHandling node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:202:17 ❯ HTMLUnknownElement.invoker node_modules/@vue/runtime-dom/dist/runtime-dom.cjs.js:638:17 ❯ HTMLUnknownElement.callTheUserObjectsOperation node_modules/jsdom/lib/jsdom/living/generated/EventListener.js:26:30 ❯ innerInvokeEventListeners node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:338:25 ❯ invokeEventListeners node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:274:3 ❯ HTMLUnknownElementImpl._dispatch node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:221:9 This error originated in "tests/components/prompt.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "Send attachment". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
tests/components/prompt.test.ts > Send attachment: tests/components/prompt.test.ts#L122
AssertionError: expected "spy" to be called with arguments: [ 'attachFile', …(1) ] Received: Number of calls: 0 ❯ tests/components/prompt.test.ts:122:25
build
Process completed with exit code 1.
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: JesseTG/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.