[GH-ISSUE #638] Enrich shutdown-failure diagnostics without breaking exact-output assertions #299

New issue

Closed

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

bsakaguchi commented

2026-10-15 18:23:37 +00:00

Owner

Originally created by @morluto on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/638

Deferred from the silent-catch sweep (#637).

Location: src/main/shutdown.ts:32 — the shutdown-failure logging/exit-code chain swallows its cause.

Problem: binding and logging the cause would change stderr/log text that exact-output assertions pin. Enriching it needs either a contract decision that the text may change (plus test updates) or a side-channel (debug log) for the cause.

Ask: decide whether shutdown-failure text is contractual; if yes, log the cause at debug level, else interpolate and update assertions.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/638 Deferred from the silent-catch sweep (#637). **Location:** `src/main/shutdown.ts:32` — the shutdown-failure logging/exit-code chain swallows its cause. **Problem:** binding and logging the cause would change stderr/log text that exact-output assertions pin. Enriching it needs either a contract decision that the text may change (plus test updates) or a side-channel (debug log) for the cause. **Ask:** decide whether shutdown-failure text is contractual; if yes, log the cause at debug level, else interpolate and update assertions.

bsakaguchi

2026-10-15 18:23:37 +00:00