TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.test frontend/javascripts/libs/resumable-upload.ts:333:31 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:404:12 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload-use-cases.spec.ts:108:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload-use-cases.spec.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 "should not upload chunk if it already exists on server)". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.test frontend/javascripts/libs/resumable-upload.ts:333:31 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:404:12 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload-use-cases.spec.ts:108:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload-use-cases.spec.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 "should not upload chunk if it already exists on server)". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.test frontend/javascripts/libs/resumable-upload.ts:333:31 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:404:12 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload-use-cases.spec.ts:108:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload-use-cases.spec.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 "should not upload chunk if it already exists on server)". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.test frontend/javascripts/libs/resumable-upload.ts:333:31 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:404:12 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload-use-cases.spec.ts:86:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload-use-cases.spec.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 "should issue GET request before POST". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.test frontend/javascripts/libs/resumable-upload.ts:333:31 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:404:12 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload-use-cases.spec.ts:86:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload-use-cases.spec.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 "should issue GET request before POST". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.test frontend/javascripts/libs/resumable-upload.ts:333:31 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:404:12 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload-use-cases.spec.ts:86:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload-use-cases.spec.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 "should issue GET request before POST". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:471:31 ❯ frontend/javascripts/test/libs/resumable-upload.spec.ts:540:13 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload.spec.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 "should generate consistent identifiers for same file". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:471:31 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload-use-cases.spec.ts:60:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload-use-cases.spec.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 "should call query function for every chunk to get latest token". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:471:31 ❯ ResumableFile.upload frontend/javascripts/libs/resumable-upload.ts:805:17 ❯ ResumableUpload.uploadNextChunk frontend/javascripts/libs/resumable-upload.ts:1249:25 ❯ ResumableUpload.upload frontend/javascripts/libs/resumable-upload.ts:1288:12 ❯ frontend/javascripts/test/libs/resumable-upload.spec.ts:529:24 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload.spec.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 "should retry and complete when an upload request times out". 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.

TypeError: Invalid URL ❯ Object.getTargetURI frontend/javascripts/libs/resumable-upload.ts:246:17 ❯ ResumableChunk.send frontend/javascripts/libs/resumable-upload.ts:471:31 ❯ frontend/javascripts/test/libs/resumable-upload.spec.ts:495:13 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'ERR_INVALID_URL', input: '/upload' } This error originated in "frontend/javascripts/test/libs/resumable-upload.spec.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 "should switch to uploading when sent". 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.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/