Catch & ignore ENOTCONN errors when piping Cypress subprocess

[flotwig]

• Closes ENOTCONN error on Windows runs #5241

User facing changelog

Fixed a bug where Cypress would exit with an ENOTCONN error at the end of a test run if using Node 12.11.0 or greater on Windows.

Additional details

Still trying to reproduce in my Windows VM, but a user in #5241 did say that this patch resolves the issue for them.

Was able to reproduce (only in cypress run) and confirmed that this patch does fix the issue for Node 12.11.0 and Windows 10.

PR Tasks

• Have tests been added/updated?

[cypress]

---

Test summary

3371 • 0 • 47 • 0

---

Run details

Project	cypress
Status	Passed
Commit	48bbe44
Started	Oct 7, 2019 4:03 PM
Ended	Oct 7, 2019 4:08 PM
Duration	04:32 💡
OS	Linux Debian - 9.8
Browser	Multiple

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[kuceb]

@flotwig why dep change to https-proxy-agent ?

[flotwig]

why dep change to https-proxy-agent ?

To fix the build - this PR hadn't been merged at the time: #5294

[bahmutov]

looks good

[michalko]

when's the new version coming ?

[TaukSnarkyAgrud]

I just want to know if there's a temp fix I can perform.
I am running async calls from a node script and this fails even when I make them await.

`await executeCypressRun('path-to-spec-redacted', "⚕️app👩‍⚕️", "💻subdomain💻", webTestDescription, "Production Environment", 35000);

    executeCypressRun('path-to-spec-redacted', "⚕️app👩‍⚕️", "📟subdomain📟", emrTestDescription, "Production Environment", 35000);

function executeCypressRun(spec, domain, subdomain, environment, usualTime){
console.log("------------------>Checkpoint1<-----------------")
return cypress.run({
spec: spec,
config: {
defaultCommandTimeout: 10000,
integrationFolder: 'path-to-integration-redacted',
trashAssetsBeforeRuns: true
}
}).then((results) => {
console.log("------------------>Chekpoint2<-----------------");
analyseThenPostToTeams(results, domain, subdomain, environment, usualTime);
});
}`

[flotwig]

@TaukSnarkyAgrud There's a 1-line patch in the original issue comment that you can use: #5241

[TaukSnarkyAgrud]

@flotwig Thanks. I saw 5241 but my understanding didn't coalesce till just now. Working now.