Support both new decorators (typescript 5.0+) and legacy decorators #507
ajlai-orkesAnnotations
18 errors and 5 warnings
|
Node.js v20 - integration v5 (shard 3/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v20 - integration v5 (shard 3/3)
Process completed with exit code 1.
|
|
SchedulerClient › Should be able to pause the schedule:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to pause schedule 'jsSdkTestSchedule_1773350675359': Schedule 'jsSdkTestSchedule_1773350675359' not found
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at SchedulerClient.pauseSchedule (src/sdk/clients/scheduler/SchedulerClient.ts:98:21)
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:136:5)
|
|
SchedulerClient › Should be able to see the result in executed schedule:
src/integration-tests/SchedulerClient.test.ts#L130
expect(received).toBeGreaterThan(expected)
Expected: > 0
Received: 0
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:130:37)
|
|
SchedulerClient › Should be able to resume the schedule:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to resume schedule 'jsSdkTestSchedule_1773350675359': Schedule 'jsSdkTestSchedule_1773350675359' not found
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at SchedulerClient.resumeSchedule (src/sdk/clients/scheduler/SchedulerClient.ts:116:21)
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:110:5)
|
|
SchedulerClient › Should be able to register a workflow and retrieve it:
src/integration-tests/SchedulerClient.test.ts#L95
expect(received).resolves.not.toThrow()
Received promise rejected instead of resolved
Rejected to value: [[Conductor SDK Error]: Failed to save schedule: Response body object should not be disturbed or locked]
at expect (node_modules/expect/build/index.js:2116:15)
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:95:17)
|
|
Node.js v22 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v22 - integration v5 (shard 2/3)
Process completed with exit code 1.
|
|
ConductorWorkflow DSL › LLM Task Builders › llmChatCompleteTask should create valid LLM task definition:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:62:21)
at ConductorWorkflow.register (src/sdk/builders/ConductorWorkflow.ts:268:5)
at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:387:7)
|
|
ConductorWorkflow DSL › Input/Output References › input/output references should work in real workflows:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:62:21)
at ConductorWorkflow.register (src/sdk/builders/ConductorWorkflow.ts:268:5)
at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:328:7)
|
|
ConductorWorkflow DSL › SubWorkflow Task › toSubWorkflowTask() should embed child workflow in parent:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:62:21)
at ConductorWorkflow.register (src/sdk/builders/ConductorWorkflow.ts:268:5)
at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:271:7)
|
|
ConductorWorkflow DSL › Fork/Join › fork() should create parallel branches with auto-join:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:62:21)
at ConductorWorkflow.register (src/sdk/builders/ConductorWorkflow.ts:268:5)
at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:234:7)
|
|
ConductorWorkflow DSL › Start Workflow › startWorkflow() with correlationId should set correlation:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:83:21)
at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:202:26)
|
|
ConductorWorkflow DSL › Start Workflow › startWorkflow() should start asynchronously and return ID:
src/integration-tests/ConductorWorkflow.test.ts#L173
thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/ConductorWorkflow.test.ts:173:9
at src/integration-tests/ConductorWorkflow.test.ts:170:11
at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:36:9)
|
|
ConductorWorkflow DSL › Execute Workflow › execute() should run workflow synchronously and return result:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow: Response body object should not be disturbed or locked
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:62:21)
at ConductorWorkflow.register (src/sdk/builders/ConductorWorkflow.ts:268:5)
at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:158:7)
|
|
Node.js v24 - integration v5 (shard 3/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v24 - integration v5 (shard 3/3)
Process completed with exit code 1.
|
|
Worker Advanced Features › MetricsCollector › should collect poll and execution metrics during workflow run:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow: Response body object should not be disturbed or locked
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:62:21)
at Object.<anonymous> (src/integration-tests/WorkerAdvanced.test.ts:94:7)
|
|
Node.js v20 - integration v5 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v22 - integration v5 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v24 - integration v5 (shard 1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v24 - integration v5 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v24 - integration v5 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|