Conversation
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
There was a problem hiding this comment.
🔧 Build Fix:
Vitest tests were failing with an EPIPE error due to race conditions in the default worker pool configuration where child processes closed communication pipes before the parent process finished sending data.
View Details
📝 Patch Details
diff --git a/apps/app/vitest.config.mts b/apps/app/vitest.config.mts
index 0866bcb..fabada1 100644
--- a/apps/app/vitest.config.mts
+++ b/apps/app/vitest.config.mts
@@ -6,6 +6,12 @@ export default defineConfig({
plugins: [react()],
test: {
environment: "jsdom",
+ pool: "threads",
+ poolOptions: {
+ threads: {
+ singleThread: true,
+ },
+ },
},
resolve: {
alias: {
Analysis
Vitest EPIPE error in worker process communication
What fails: Vitest test runner fails with EPIPE error after tests complete successfully in apps/app directory
How to reproduce:
cd apps/app
NODE_ENV=test pnpm run testResult:
Tests pass but process fails with:
Error: write EPIPE
at ChildProcess.target._send (node:internal/child_process:877:20)
at ForksPoolWorker.send (...vitest/dist/chunks/cli-api.D24RdiHp.js:6559:13)
errno: -32, code: 'EPIPE', syscall: 'write'The error occurs in Vitest's worker process communication system when child processes close their communication pipes before the parent process finishes sending data.
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/github_actions/actions/setup-node-6
branch
1 participant
Bumps actions/setup-node from 4 to 6.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
2028fbcLimit automatic caching to npm, update workflows and documentation (#1374)1342781Bump actions/publish-action from 0.3.0 to 0.4.0 (#1362)89d709dBump prettier from 2.8.8 to 3.6.2 (#1334)cd2651cBump ts-jest from 29.1.2 to 29.4.1 (#1336)a0853c2Bump actions/checkout from 4 to 5 (#1345)b7234ccUpgrade action to use node24 (#1325)d7a1131Enhance caching in setup-node with automatic package manager detection (#1348)5e2628cBumps form-data (#1332)65becefBump undici from 5.28.5 to 5.29.0 (#1295)7e24a65Bump uuid from 9.0.1 to 11.1.0 (#1273)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)