Skip to content

Conversation

@alexsch01
Copy link
Contributor

@alexsch01 alexsch01 commented Oct 24, 2025

Additional details

Steps to test

How has the user experience changed?

PR Tasks


Note

Ignore EPIPE from the config child process (prevents terminal error after CTRL+C) and add the corresponding bugfix to the changelog.

  • Core/IPC:
    • In packages/data-context/src/data/ProjectConfigIpc.ts, handleChildProcessError() now early-returns on err.code === 'EPIPE' after cleanup to suppress noisy errors post-CTRL+C.
  • Changelog:
    • Add bugfix entry in cli/CHANGELOG.md for avoiding EPIPE error after CTRL+C.

Written by Cursor Bugbot for commit e0b4158. This will update automatically on new commits. Configure here.

@cypress-app-bot
Copy link
Collaborator

@jennifer-shehane
Copy link
Member

@alexsch01 Any thoughts on how to test this?

@alexsch01
Copy link
Contributor Author

alexsch01 commented Oct 27, 2025

@jennifer-shehane for manually testing this.....

send (event: string, ...args: any[]) {

   send (event: string, ...args: any[]) {
+    if (event === "preprocessor:close") {
+      Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, 4000)
+    }
  • above adds an synchronous wait of 4000 ms

with a spec file such as

it("", () => {
cy.wrap(0).should("eq", 0)
})

run yarn cypress:run --project PROJECT_DIR --no-exit

  • let cypress spec go all the way to the end
  • then CTRL-C with and without this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error: write EPIPE after CTRL+C in terminal

3 participants