[GH-ISSUE #165] setupInstallFailure default branch over-collapses distinct install failures #112

New issue

Closed

opened 2026-10-15 18:21:15 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:21:15 +00:00

Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/165

Summary

Several Hopper installer failure reasons are collapsed to download_failed, reducing signal quality for users and automation.

Evidence

src/application/SetupInstallFailure.ts maps many distinct installer outcomes into download_failed via the default branch:
- mapped as code: "download_failed" in lines 87-93.
Distinct reasons exist in SetupFailureCode and installer internals that are currently not preserved (e.g. destination_exists, mount, bundle, copy).

Impact

Users receive a generic remediation even for non-network/dependency failures, which hinders accurate recovery guidance and can lead to repeated failed attempts.

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/165 ## Summary Several Hopper installer failure reasons are collapsed to `download_failed`, reducing signal quality for users and automation. ## Evidence - `src/application/SetupInstallFailure.ts` maps many distinct installer outcomes into `download_failed` via the `default` branch: - mapped as `code: "download_failed"` in lines 87-93. - Distinct reasons exist in `SetupFailureCode` and installer internals that are currently not preserved (e.g. `destination_exists`, `mount`, `bundle`, `copy`). ## Impact Users receive a generic remediation even for non-network/dependency failures, which hinders accurate recovery guidance and can lead to repeated failed attempts.

bsakaguchi

2026-10-15 18:21:15 +00:00