fix(watcher): remove emitRecentHistory from watcher startup entirely #1175
im4codesci.yml
on: push
Matrix: unit-tests
Lint
26s
Typecheck
31s
Secret Scan (gitleaks)
5s
Server Unit Tests
45s
Unit Tests (macOS)
2m 10s
Unit Tests (Windows)
48s
Unit Tests (Windows ConPTY)
58s
Server DB Integration Tests
49s
Repo Provider Integration Tests
Coverage Report
Android Release Build
Publish to npm
0s
Annotations
15 errors and 17 warnings
|
Unit Tests (Node 20)
Process completed with exit code 1.
|
|
test/daemon/jsonl-watcher.test.ts > stable eventId generation > generates deterministic eventIds based on byte offset:
test/daemon/jsonl-watcher.test.ts#L665
AssertionError: expected 0 to be greater than 0
❯ test/daemon/jsonl-watcher.test.ts:665:28
|
|
test/daemon/jsonl-watcher.test.ts > emitRecentHistory — returns last N lines > returns the LAST 500 events, not the first 500 from tail chunk:
test/daemon/jsonl-watcher.test.ts#L540
AssertionError: expected [] to include 'Message number 599'
❯ test/daemon/jsonl-watcher.test.ts:540:23
|
|
Unit Tests (Node 24)
The strategy configuration was canceled because "unit-tests._20" failed
|
|
Unit Tests (Node 24)
The operation was canceled.
|
|
test/daemon/jsonl-watcher.test.ts > stable eventId generation > generates deterministic eventIds based on byte offset:
test/daemon/jsonl-watcher.test.ts#L665
AssertionError: expected 0 to be greater than 0
❯ test/daemon/jsonl-watcher.test.ts:665:28
|
|
test/daemon/jsonl-watcher.test.ts > emitRecentHistory — returns last N lines > returns the LAST 500 events, not the first 500 from tail chunk:
test/daemon/jsonl-watcher.test.ts#L540
AssertionError: expected [] to include 'Message number 599'
❯ test/daemon/jsonl-watcher.test.ts:540:23
|
|
Unit Tests (Node 22)
The strategy configuration was canceled because "unit-tests._20" failed
|
|
Unit Tests (Node 22)
The operation was canceled.
|
|
test/daemon/jsonl-watcher.test.ts > stable eventId generation > generates deterministic eventIds based on byte offset:
test/daemon/jsonl-watcher.test.ts#L665
AssertionError: expected 0 to be greater than 0
❯ test/daemon/jsonl-watcher.test.ts:665:28
|
|
test/daemon/jsonl-watcher.test.ts > emitRecentHistory — returns last N lines > returns the LAST 500 events, not the first 500 from tail chunk:
test/daemon/jsonl-watcher.test.ts#L540
AssertionError: expected [] to include 'Message number 599'
❯ test/daemon/jsonl-watcher.test.ts:540:23
|
|
Unit Tests (macOS)
Process completed with exit code 1.
|
|
test/daemon/jsonl-watcher.test.ts > stable eventId generation > generates deterministic eventIds based on byte offset:
test/daemon/jsonl-watcher.test.ts#L665
AssertionError: expected 0 to be greater than 0
❯ test/daemon/jsonl-watcher.test.ts:665:28
|
|
test/daemon/jsonl-watcher.test.ts > emitRecentHistory — returns last N lines > returns the LAST 500 events, not the first 500 from tail chunk:
test/daemon/jsonl-watcher.test.ts#L540
AssertionError: expected [] to include 'Message number 599'
❯ test/daemon/jsonl-watcher.test.ts:540:23
|
|
test/daemon/jsonl-watcher-refresh.test.ts > jsonl watcher refresh() > refresh reads newly appended content for its own tracked file:
test/daemon/jsonl-watcher-refresh.test.ts#L40
Error: waitUntil timeout
❯ waitUntil test/daemon/jsonl-watcher-refresh.test.ts:40:9
❯ test/daemon/jsonl-watcher-refresh.test.ts:87:5
|
|
Secret Scan (gitleaks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, gitleaks/gitleaks-action@v2. 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/
|
|
Lint
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. 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/
|
|
Lint:
src/daemon/p2p-orchestrator.ts#L205
'skippedSet' is assigned a value but never used
|
|
Lint:
src/daemon/jsonl-watcher.ts#L507
'emitRecentHistory' is defined but never used
|
|
Lint:
src/daemon/command-handler.ts#L2213
'UPLOAD_DIR' is assigned a value but never used
|
|
Lint:
src/daemon/command-handler.ts#L2087
'cliEntry' is assigned a value but never used
|
|
Typecheck
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. 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/
|
|
Web Tests (Components)
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. 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/
|
|
Web Tests (Unit)
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. 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/
|
|
Server Unit Tests
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. 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/
|
|
Unit Tests (Windows)
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. 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/
|
|
Server DB Integration Tests
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. 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/
|
|
Unit Tests (Windows ConPTY)
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. 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/
|
|
Unit Tests (Node 20)
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. 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/
|
|
Unit Tests (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 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/
|
|
Unit Tests (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 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/
|
|
Unit Tests (macOS)
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. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
gitleaks-results.sarif
|
367 Bytes |
sha256:039bc35bb0408c6810804185fe2f4fe40d55eda7d7d6b4dd38ddda5e9cf65ec8
|
|