Avoid writing error file if client is closed during bundle compose

[vinistock]

Motivation

This PR addresses one of the telemetry errors we see when using the new launcher mode. If the editor is closed while we're in the middle of composing the bundle, the server is not yet fully booted and cannot respond to shutdown requests.

If the client disconnects, closing their ends of the stdio pipes, the bundle install process may continue to try writing output to stderr, which results in raising Errno::EPIPE. When the error is raised, we write that error to the install_error file and then the process exists soon after.

The next time the language server is booted, it sees that the install_error file is there and reports that as an error, but this situation doesn't actually indicate a bug. It just means the user closed the editor before we were done composing the bundle. The next time they open it, we'll compose from scratch.

Implementation

Started rescuing Errno::EPIPE when running bundle install and clearing the install_error file, so that we don't report this scenario to telemetry and simply shutdown gracefully.

Automated Tests

Added a test to verify that the install_error file is not created when one of these happen.

[vinistock]

• Avoid writing error file if client is closed during bundle compose #3649 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label graphite-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[egiurleo]

Woohoo!