feat: move chassis-srv and resource-base-interface #270
Triggered via pull request
September 11, 2025 17:51
Vilsol
Status
Success
Total duration
1m 21s
Artifacts
–
build-test-gql-bot.yaml
on: pull_request
build
/
build
34s
test
/
test
40s
Annotations
2 errors
|
Unhandled error:
packages/gql-bot/src/client.ts#L216
Error: {"code":403,"message":"Access denied"}
❯ Client.post src/client.ts:216:13
❯ processTicksAndRejections node:internal/process/task_queues:105:5
❯ YamlStreamReadTransformer.<anonymous> src/job_processor_gql.ts:87:32
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { isOperational: true }
This error originated in "test/job_processor.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 "a job should error when encountering IoRestorecommerceStatusStatus". 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:
packages/gql-bot/src/client.ts#L216
Error: {"code":403,"message":"Access denied"}
❯ Client.post src/client.ts:216:13
❯ processTicksAndRejections node:internal/process/task_queues:105:5
❯ YamlStreamReadTransformer.<anonymous> src/job_processor_gql.ts:87:32
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { isOperational: true }
This error originated in "test/job_processor.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 "a job should error when encountering IoRestorecommerceStatusOperationStatus". 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.
|