Upgrade trunk to 1.22.13-beta.17

[trunk-open-pr-bot]

cli upgraded: 1.22.12 → 1.22.13-beta.17

1 linter was upgraded:

• eslint 9.24.0 → 9.25.1

This PR was generated by the Trunk Action. For more info, see our docs or reach out on Slack.

[trunk-io]

⏱️ 1h 8m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
Linter Tests ubuntu-latest	22m	🟩
Linter Tests macOS	20m	🟩
Tool Tests (ubuntu-latest)	11m	🟩
Tool Tests (macOS)	6m	🟩
Action Tests	3m	🟩 🟩
CodeQL-Build	3m	🟩 🟩
Trunk Check runner [linux]	2m	🟩 🟩
Repo Tests / Plugin Tests	38s	🟩
Detect changed files	8s	🟩 🟩
Aggregate Test Results	1s	🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[trunk-staging-io]

     

Failed Test	Failure Summary	Logs
Testing tool jq jq --version	The write operation failed with an EPIPE error, indicating that the pipe was closed unexpectedly.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[trunk-staging-io]

     

View Full Report ↗︎ ⋅ Docs

[trunk-staging-io]

     

View Full Report ↗︎ ⋅ Docs

[trunk-io]

     

Failed Test	Failure Summary	Logs
Testing tool jq jq --version	The write operation failed with an EPIPE error, indicating that the pipe was closed unexpectedly.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[chip-agent]

Summary:
The test Testing tool jq jq --version is failing with a write EPIPE error. This error suggests a broken pipe, which typically occurs when a program attempts to write to a pipe that has been closed by the reading end. The PR upgrades the trunk cli version and eslint.

Root Cause Analysis:
The write EPIPE error often indicates a problem with how the test interacts with the tool it's testing (in this case, jq). It's possible that the upgraded eslint or trunk cli is causing the jq command to exit prematurely or in an unexpected way, leading to the broken pipe. The error occurs during the TrunkToolDriver.run call, suggesting the issue arises when running the tool within the test environment. This could be due to changes in how the CLI handles input/output streams or how it interacts with the underlying system.

Resolution Plan:

1. Investigate the interaction with jq: Examine the test setup and execution flow in tests/driver/driver.ts and tests/index.ts to understand how jq is being invoked and how its output is being handled.
2. Check for CLI changes: Review the changelogs for the upgraded eslint and trunk cli versions to identify any changes that might affect how they interact with external commands or handle input/output streams.
3. Add error handling: Implement more robust error handling in TrunkToolDriver.run to catch potential exceptions or unexpected exit codes from the tool being executed. This can help pinpoint the exact cause of the broken pipe.
4. Retry the test: The error could be transient. Re-running the test might resolve the issue.
5. Downgrade to previous versions: If the error persists, try downgrading eslint and trunk cli to the previous versions to see if the issue is related to the upgrades.

Since I don't have enough information to pinpoint the exact cause, the user should investigate further using the above plan.

---

Is this helpful? Click the 👍/👎 buttons below to let us know!

Icons by Icons8