examples: 14 ARCP-primitive samples translated from python-sdk #2
nficanoAnnotations
20 errors and 2 warnings
|
test (node 22):
examples/lease_revocation/main.ts#L50
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 22):
examples/heartbeats/main.ts#L119
Type 'undefined' is not assignable to type 'string' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the type of the target.
|
|
test (node 22):
examples/handoff/main.ts#L82
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 22):
examples/handoff/main.ts#L51
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 22):
examples/extensions/main.ts#L39
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 22):
examples/capability_negotiation/main.ts#L128
Property 'peer' comes from an index signature, so it must be accessed with ['peer'].
|
|
test (node 22):
examples/capability_negotiation/main.ts#L125
Property 'kind' comes from an index signature, so it must be accessed with ['kind'].
|
|
test (node 22):
examples/capability_negotiation/main.ts#L124
Property 'kind' comes from an index signature, so it must be accessed with ['kind'].
|
|
test (node 22):
examples/capability_negotiation/main.ts#L121
Property 'tenant' comes from an index signature, so it must be accessed with ['tenant'].
|
|
test (node 22):
examples/cancellation/main.ts#L58
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 24):
examples/lease_revocation/main.ts#L50
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 24):
examples/heartbeats/main.ts#L119
Type 'undefined' is not assignable to type 'string' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the type of the target.
|
|
test (node 24):
examples/handoff/main.ts#L82
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 24):
examples/handoff/main.ts#L51
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 24):
examples/extensions/main.ts#L39
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 24):
examples/capability_negotiation/main.ts#L128
Property 'peer' comes from an index signature, so it must be accessed with ['peer'].
|
|
test (node 24):
examples/capability_negotiation/main.ts#L125
Property 'kind' comes from an index signature, so it must be accessed with ['kind'].
|
|
test (node 24):
examples/capability_negotiation/main.ts#L124
Property 'kind' comes from an index signature, so it must be accessed with ['kind'].
|
|
test (node 24):
examples/capability_negotiation/main.ts#L121
Property 'tenant' comes from an index signature, so it must be accessed with ['tenant'].
|
|
test (node 24):
examples/cancellation/main.ts#L58
Argument of type '{ message: string; }' is not assignable to parameter of type 'string'.
|
|
test (node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
test (node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|