Skip to content

161 Add API calls UUID Seed lIst #167

161 Add API calls UUID Seed lIst

161 Add API calls UUID Seed lIst #167

Triggered via pull request June 21, 2024 12:56
Status Failure
Total duration 2m 29s
Artifacts

react-frontend-workflows.yml

on: pull_request
build-and-push-gcr  /  build-push-image
2m 3s
build-and-push-gcr / build-push-image
markdown-check  /  markdown-check
15s
markdown-check / markdown-check
repo-standard  /  validate-name
31s
repo-standard / validate-name
lint-test  /  lint-test
36s
lint-test / lint-test
build-and-push-gcr  /  remove-old-image
9s
build-and-push-gcr / remove-old-image
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 8 warnings
Unhandled error: src/components/body/microscope_feed/MicroscopeFeed.tsx#L153
TypeError: Cannot read properties of undefined (reading 'length') ❯ src/components/body/microscope_feed/MicroscopeFeed.tsx:153:32 This error originated in "src/root/body/body.test.tsx" 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 "renders Body component". 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.
Unhandled error: src/components/body/microscope_feed/MicroscopeFeed.tsx#L153
TypeError: Cannot read properties of undefined (reading 'length') ❯ src/components/body/microscope_feed/MicroscopeFeed.tsx:153:32 ❯ runNextTicks node:internal/process/task_queues:60:5 ❯ listOnTimeout node:internal/timers:538:9 ❯ processTimers node:internal/timers:512:7 This error originated in "src/root/body/body.test.tsx" 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 "renders Microscope Feed". 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.
Unhandled error: src/components/body/microscope_feed/MicroscopeFeed.tsx#L153
TypeError: Cannot read properties of undefined (reading 'length') ❯ src/components/body/microscope_feed/MicroscopeFeed.tsx:153:32 ❯ runNextTicks node:internal/process/task_queues:60:5 ❯ listOnTimeout node:internal/timers:538:9 ❯ processTimers node:internal/timers:512:7 This error originated in "src/root/body/body.test.tsx" 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 "renders Storage Directory". 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.
Unhandled error: src/components/body/microscope_feed/MicroscopeFeed.tsx#L153
TypeError: Cannot read properties of undefined (reading 'length') ❯ src/components/body/microscope_feed/MicroscopeFeed.tsx:153:32 ❯ runNextTicks node:internal/process/task_queues:60:5 ❯ listOnTimeout node:internal/timers:538:9 ❯ processTimers node:internal/timers:512:7 This error originated in "src/root/body/body.test.tsx" 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 "renders Image Cache". 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.
Unhandled error: src/components/body/microscope_feed/MicroscopeFeed.tsx#L153
TypeError: Cannot read properties of undefined (reading 'length') ❯ src/components/body/microscope_feed/MicroscopeFeed.tsx:153:32 ❯ runNextTicks node:internal/process/task_queues:60:5 ❯ listOnTimeout node:internal/timers:538:9 ❯ processTimers node:internal/timers:512:7 This error originated in "src/root/body/body.test.tsx" 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 "renders Classification Results". 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.
lint-test / lint-test
Process completed with exit code 1.
markdown-check / markdown-check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
markdown-check / markdown-check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
repo-standard / validate-name
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/github-script@v5. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
repo-standard / validate-name
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint-test / lint-test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-and-push-gcr / build-push-image
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-and-push-gcr / build-push-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-gcr / remove-old-image
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.