Skip to content

Unify item and group data structures #434

Unify item and group data structures

Unify item and group data structures #434

Triggered via pull request January 8, 2025 12:14
Status Failure
Total duration 1m 10s
Artifacts

node.js.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 3 warnings
check
Process completed with exit code 1.
lint
Process completed with exit code 1.
tests/endToEnd/pages.test.ts > Homepage loads: tests/endToEnd/pages.test.ts#L15
AssertionError: promise rejected "Error: ApiError: [500] Request got status… { …(2) }" instead of resolving ❯ tests/endToEnd/pages.test.ts:15:32 Caused by: Caused by: Error: ApiError: [500] Request got status code 500 ❯ text src/endpoints/fetch/response.ts:15:11 ❯ tests/endToEnd/pages.test.ts:15:3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { error: 'Request got status code 500', code: 500 }
tests/endToEnd/pages.test.ts > Item page loads: tests/endToEnd/pages.test.ts#L28
AssertionError: promise rejected "Error: ApiError: [500] Request got status… { …(2) }" instead of resolving ❯ tests/endToEnd/pages.test.ts:28:43 Caused by: Caused by: Error: ApiError: [500] Request got status code 500 ❯ text src/endpoints/fetch/response.ts:15:11 ❯ tests/endToEnd/pages.test.ts:28:3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { error: 'Request got status code 500', code: 500 }
tests/backend/item/file.delete.test.ts > 401 > Invalid token > Token has invalid structure: tests/backend/tokenCase.ts#L28
AssertionError: expected Error: ApiError: [null] fetchFn is not a … { …(2) } to match object { code: 401 } (1 matching property omitted from actual) - Expected + Received - Object { - "code": 401, + ApiError { + "code": null, } ❯ tests/backend/tokenCase.ts:28:7
tests/backend/item/file.delete.test.ts > 401 > Invalid token > Token has valid structure but incorrect signature: tests/backend/tokenCase.ts#L41
AssertionError: expected Error: ApiError: [null] fetchFn is not a … { …(2) } to match object { code: 401 } (1 matching property omitted from actual) - Expected + Received - Object { - "code": 401, + ApiError { + "code": null, } ❯ tests/backend/tokenCase.ts:41:7
tests/backend/item/file.post.test.ts > 401 > Invalid token > Token has invalid structure: tests/backend/tokenCase.ts#L28
AssertionError: expected Error: ApiError: [null] fetchFn is not a … { …(2) } to match object { code: 401 } (1 matching property omitted from actual) - Expected + Received - Object { - "code": 401, + ApiError { + "code": null, } ❯ tests/backend/tokenCase.ts:28:7
tests/backend/item/file.post.test.ts > 401 > Invalid token > Token has valid structure but incorrect signature: tests/backend/tokenCase.ts#L41
AssertionError: expected Error: ApiError: [null] fetchFn is not a … { …(2) } to match object { code: 401 } (1 matching property omitted from actual) - Expected + Received - Object { - "code": 401, + ApiError { + "code": null, } ❯ tests/backend/tokenCase.ts:41:7
tests/backend/item/file.put.test.ts > 401 > Invalid token > Token has invalid structure: tests/backend/tokenCase.ts#L28
AssertionError: expected Error: ApiError: [null] fetchFn is not a … { …(2) } to match object { code: 401 } (1 matching property omitted from actual) - Expected + Received - Object { - "code": 401, + ApiError { + "code": null, } ❯ tests/backend/tokenCase.ts:28:7
tests/backend/item/file.put.test.ts > 401 > Invalid token > Token has valid structure but incorrect signature: tests/backend/tokenCase.ts#L41
AssertionError: expected Error: ApiError: [null] fetchFn is not a … { …(2) } to match object { code: 401 } (1 matching property omitted from actual) - Expected + Received - Object { - "code": 401, + ApiError { + "code": null, } ❯ tests/backend/tokenCase.ts:41:7
tests/backend/item/info.put.test.ts > Success > Sections > Accepts valid package info: tests/backend/item/info.put.test.ts#L103
AssertionError: promise rejected "Error: ApiError: [400] StructError: At pa… { …(2) }" instead of resolving ❯ tests/backend/item/info.put.test.ts:103:51 Caused by: Caused by: Error: ApiError: [400] StructError: At path: sections.0 -- Expected the value to satisfy a union of `type | type | type | type | type | type`, but received: [object Object] ❯ json src/endpoints/fetch/response.ts:49:11 ❯ tests/backend/item/info.put.test.ts:103:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { error: 'StructError: At path: sections.0 -- Expected the value to satisfy a union of `type | type | type | type | type | type`, but received: [object Object]', code: 400 }
tests/backend/item/info.put.test.ts > 400 > Section data > Rejects sections with invalid titles ('Empty string'): tests/backend/item/info.put.test.ts#L191
AssertionError: promise resolved "{}" instead of rejecting - Expected + Received - [Error: rejected promise] + Object {} ❯ tests/backend/item/info.put.test.ts:191:51
check
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636