Skip to content

feature: inline parameter #475

feature: inline parameter

feature: inline parameter #475

Triggered via pull request January 8, 2025 00:05
Status Failure
Total duration 1m 52s
Artifacts

ts-sdk-tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

9 errors
src/functions/datasets/datasets.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"Trieve is currently under extended load and we are working to autoscale. If you continue facing this issue, please send an email to [email protected] with 'request timeout' in the subject line and we will get back to you as soon as possible."} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/datasets/datasets.test.ts:14:18
src/functions/datasets/datasets.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"BadRequest: Failed to get events"} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/datasets/datasets.test.ts:14:18
src/functions/datasets/datasets.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"BadRequest: Failed to get events"} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/datasets/datasets.test.ts:14:18
src/functions/datasets/datasets.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"BadRequest: Failed to get events"} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/datasets/datasets.test.ts:14:18
src/functions/events/events.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"Trieve is currently under extended load and we are working to autoscale. If you continue facing this issue, please send an email to [email protected] with 'request timeout' in the subject line and we will get back to you as soon as possible."} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/events/events.test.ts:14:18
src/functions/events/events.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"BadRequest: Failed to get events"} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/events/events.test.ts:14:18
src/functions/events/events.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"BadRequest: Failed to get events"} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/events/events.test.ts:14:18
src/functions/events/events.test.ts > Events Tests > getEventsForDataset: clients/ts-sdk/src/fetch-client.ts#L180
Error: HTTP error! status: {"message":"BadRequest: Failed to get events"} Payload {} route: post https://api.trieve.ai/api/dataset/events ❯ TrieveFetchClient.fetch src/fetch-client.ts:180:13 ❯ TrieveSDK.getEventsForDataset src/functions/events/index.ts:32:10 ❯ src/functions/events/events.test.ts:14:18
tests
Process completed with exit code 1.