feat: close Week 5 review findings — idle timeout, log-level, profile threading, docs #19
ci.yml
on: pull_request
quality-gates
11m 6s
quality-gates-macos
1m 34s
Annotations
10 errors and 2 warnings
|
test/e2e/renderer-errors.test.ts > renderer error paths e2e > returns an error for screenshot profiles beyond the schema maximum length:
test/helpers.ts#L125
AssertionError: expected 9 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 9
❯ createSession test/helpers.ts:125:25
❯ test/e2e/renderer-errors.test.ts:78:23
|
|
test/e2e/renderer-errors.test.ts > renderer error paths e2e > returns an error for unknown screenshot profiles:
test/helpers.ts#L125
AssertionError: expected 9 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 9
❯ createSession test/helpers.ts:125:25
❯ test/e2e/renderer-errors.test.ts:64:23
|
|
test/e2e/hello-prompt.test.ts > hello-prompt e2e > signal handling:
test/e2e/hello-prompt.test.ts#L238
TypeError: Cannot read properties of undefined (reading 'sessionId')
❯ test/e2e/hello-prompt.test.ts:238:45
|
|
test/e2e/hello-prompt.test.ts > hello-prompt e2e > paste and exit-code:
test/e2e/hello-prompt.test.ts#L185
TypeError: Cannot read properties of undefined (reading 'sessionId')
❯ test/e2e/hello-prompt.test.ts:185:45
|
|
test/e2e/hello-prompt.test.ts > hello-prompt e2e > full interaction flow:
test/e2e/hello-prompt.test.ts#L56
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test/e2e/hello-prompt.test.ts:56:31
|
|
test/e2e/export-fixtures.test.ts > export fixture e2e > runs the full export pipeline and records every artifact in the manifest:
test/e2e/export-fixtures.test.ts#L61
AssertionError: expected 9 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 9
❯ runCliEnvelope test/e2e/export-fixtures.test.ts:61:25
❯ createFixtureSession test/e2e/export-fixtures.test.ts:97:26
❯ test/e2e/export-fixtures.test.ts:422:23
|
|
test/e2e/export-fixtures.test.ts > export fixture e2e > supports post-mortem snapshot, screenshot, and asciicast export after a crash:
test/e2e/export-fixtures.test.ts#L61
AssertionError: expected 9 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 9
❯ runCliEnvelope test/e2e/export-fixtures.test.ts:61:25
❯ createFixtureSession test/e2e/export-fixtures.test.ts:97:26
❯ test/e2e/export-fixtures.test.ts:350:23
|
|
test/e2e/export-fixtures.test.ts > export fixture e2e > captures alt-screen content live and replays the restored main screen after exit:
test/e2e/export-fixtures.test.ts#L61
AssertionError: expected 9 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 9
❯ runCliEnvelope test/e2e/export-fixtures.test.ts:61:25
❯ createFixtureSession test/e2e/export-fixtures.test.ts:97:26
❯ test/e2e/export-fixtures.test.ts:270:23
|
|
test/e2e/export-fixtures.test.ts > export fixture e2e > exports color-grid output as an asciicast with ANSI color sequences:
test/e2e/export-fixtures.test.ts#L61
AssertionError: expected 9 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 9
❯ runCliEnvelope test/e2e/export-fixtures.test.ts:61:25
❯ createFixtureSession test/e2e/export-fixtures.test.ts:97:26
❯ test/e2e/export-fixtures.test.ts:227:23
|
|
test/e2e/export-fixtures.test.ts > export fixture e2e > captures a color-grid screenshot with a non-trivial PNG artifact:
test/e2e/export-fixtures.test.ts#L61
AssertionError: expected 9 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 9
❯ runCliEnvelope test/e2e/export-fixtures.test.ts:61:25
❯ createFixtureSession test/e2e/export-fixtures.test.ts:97:26
❯ test/e2e/export-fixtures.test.ts:193:23
|
|
quality-gates-macos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@v3. 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/
|
|
quality-gates
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@v3. 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/
|