feat: safe timing helper (#5080) #541
thetutlagechecks.yml
on: push
Matrix: lint / lint
Matrix: test / test_linux
Matrix: test / test_windows
Matrix: typecheck / typecheck
Annotations
25 errors and 8 warnings
|
test / test_linux (latest)
Process completed with exit code 1.
|
|
Request validator / use custom error reporter:
tests/request_validator.spec.ts#L279
Planned for 1 assertion, but ran 2
|
|
Request validator / use custom messages provider:
tests/request_validator.spec.ts#L267
expected [ { …(3) } ] to deeply equal [ { field: 'username', …(2) } ]
- Expected - 2
+ Received + 2
Array [
Object {
"field": "username",
- "message": "The selected username is invalid",
- "rule": "notIn",
+ "message": "The value is missing",
+ "rule": "required",
},
]
|
|
Request validator / pass metadata to validator:
tests/request_validator.spec.ts#L174
Planned for 1 assertion, but ran 2
|
|
Request validator / perform validation on request data using request validator:
tests/request_validator.spec.ts#L60
expected [ { …(3) } ] to deeply equal [ { field: 'username', …(2) } ]
- Expected - 1
+ Received + 1
Array [
Object {
"field": "username",
"message": "The username field must be defined",
- "rule": "validations.required",
+ "rule": "required",
},
]
|
|
test / test_linux (latest):
index.ts#L1
'foo' is declared but its value is never read.
|
|
test / test_linux (latest):
index.ts#L1
'foo' is declared but its value is never read.
|
|
test / test_linux (lts/krypton)
The strategy configuration was canceled because "test.test_linux.latest" failed
|
|
test / test_linux (lts/krypton)
Process completed with exit code 1.
|
|
Request validator / use custom error reporter:
tests/request_validator.spec.ts#L279
Planned for 1 assertion, but ran 2
|
|
Request validator / use custom messages provider:
tests/request_validator.spec.ts#L267
expected [ { …(3) } ] to deeply equal [ { field: 'username', …(2) } ]
- Expected - 2
+ Received + 2
Array [
Object {
"field": "username",
- "message": "The selected username is invalid",
- "rule": "notIn",
+ "message": "The value is missing",
+ "rule": "required",
},
]
|
|
Request validator / pass metadata to validator:
tests/request_validator.spec.ts#L174
Planned for 1 assertion, but ran 2
|
|
Request validator / perform validation on request data using request validator:
tests/request_validator.spec.ts#L60
expected [ { …(3) } ] to deeply equal [ { field: 'username', …(2) } ]
- Expected - 1
+ Received + 1
Array [
Object {
"field": "username",
"message": "The username field must be defined",
- "rule": "validations.required",
+ "rule": "required",
},
]
|
|
test / test_linux (lts/krypton):
index.ts#L1
'foo' is declared but its value is never read.
|
|
test / test_linux (lts/krypton):
index.ts#L1
'foo' is declared but its value is never read.
|
|
test / test_windows (lts/krypton)
Process completed with exit code 1.
|
|
Request validator / use custom error reporter:
tests/request_validator.spec.ts#L279
Planned for 1 assertion, but ran 2
|
|
Request validator / use custom messages provider:
tests/request_validator.spec.ts#L267
expected [ { …(3) } ] to deeply equal [ { field: 'username', …(2) } ]
- Expected - 2
+ Received + 2
Array [
Object {
"field": "username",
- "message": "The selected username is invalid",
- "rule": "notIn",
+ "message": "The value is missing",
+ "rule": "required",
},
]
|
|
Request validator / pass metadata to validator:
tests/request_validator.spec.ts#L174
Planned for 1 assertion, but ran 2
|
|
Request validator / perform validation on request data using request validator:
tests/request_validator.spec.ts#L60
expected [ { …(3) } ] to deeply equal [ { field: 'username', …(2) } ]
- Expected - 1
+ Received + 1
Array [
Object {
"field": "username",
"message": "The username field must be defined",
- "rule": "validations.required",
+ "rule": "required",
},
]
|
|
test / test_windows (lts/krypton):
index.ts#L1
'foo' is declared but its value is never read.
|
|
test / test_windows (lts/krypton):
index.ts#L1
'foo' is declared but its value is never read.
|
|
test / test_windows (latest)
The strategy configuration was canceled because "test.test_windows.lts_krypton" failed
|
|
test / test_windows (latest)
The operation was canceled.
|
|
test / test_windows (latest):
index.ts#L1
'foo' is declared but its value is never read.
|
|
typecheck / typecheck (lts/krypton)
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 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/
|
|
lint / lint (lts/krypton)
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 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/
|
|
lint / lint (latest)
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 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/
|
|
typecheck / typecheck (latest)
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 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/
|
|
test / test_linux (latest)
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 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/
|
|
test / test_linux (lts/krypton)
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 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/
|
|
test / test_windows (lts/krypton)
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 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/
|
|
test / test_windows (latest)
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 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/
|