Skip to content

fix(runtime): stop immediately on fatal self-exit signals - #46

Merged
mremond merged 5 commits into
mainfrom
fm/task-a9639ed2
Nov 15, 2026
Merged

mremond merged 5 commits into
mainfrom
fm/task-a9639ed2

Conversation

@mremond

@mremond mremond commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Why

A native process could continue after a fatal self-exit and report a later error instead.

What changed

  • Fatal self-signals stop before later expressions, catch handlers or cleanup.
  • Ordinary and already-trapped exit-shaped messages remain messages.
  • Pending normal self-signals match BEAM after trapping changes.
  • One shared regression exercises the same behavior natively and on BEAM.

Before and after

Before: All six fatal self-signal probe cases ran later body and cleanup effects and reported a later error.

After: All six fatal cases retain BEAM's reason without later effects, and pending trapped-normal signals remain nonfatal.

This changes native process termination and signal handling, not an on-screen interface.

Checked

Live validation: Demonstrated for this version. 4 of 4 scenarios driven live in the product.

Scenario Result Evidence
Fatal self-signals ✅ Passed live Accepted monitor/effect and pending-normal proof is retained through independent interaction review.
Ordinary and trapped exit-shaped messages ✅ Passed live Accepted mailbox and delivery controls remain applicable; no local scenario was repeated.
Shared native and BEAM regression ✅ Passed live The unchanged 94-case fixture retains ten successful runs per engine/scheduler mode.
Retained local and fresh combined hosted gate ✅ Passed live Retained local proof has 2,188 Rust passes, 497 native passes and 60 outcomes; the current hosted gate has 18 successes and three intentional skips.
  • Independent code and interaction review: No remaining findings; the accepted runtime proof applies unchanged after the conflict repairs.
How it was checked

The accepted macOS arm64 local gate, shutdown journey and edited-test repetitions are retained, not described as fresh runs after the conflict repairs.

Independent interaction reviews confirmed applicability of the unchanged fatal, mailbox and shared-regression proof.

Fresh combined-version workspace lint/tests, compiler builds, all native shards, integrations and cross-compiles passed on their hosted platforms.

The same expanded fixture previously passed ten consecutive times each on BEAM and native default/single scheduler modes; no redundant matrix was run.

Risk

Risk above low: Blast radius, medium — Touches signal delivery and mailbox metadata across several runtime paths.; Novelty, medium — Adds per-signal metadata beside the existing mailbox ring.

Full risk assessment
Dimension Level Why
Blast radius medium Touches signal delivery and mailbox metadata across several runtime paths.
Behavior low Corrects fatal self-exit ordering and preserves nonfatal message behavior.
Undo low Revert needs no data migration or settings change.
Evidence low Accepted native/BEAM proof is retained and fresh combined hosted gates pass.
Sensitivity low No sign-ins, secrets, payments or persisted user data change.
Novelty medium Adds per-signal metadata beside the existing mailbox ring.
Dependencies low No dependencies change.
Not done

Windows execution was not run.

One Rust test remains ignored and two native fixtures require missing external modules.

The hosted change map intentionally skipped both editor plugins and the packaging trial.

Pipeline

Updates from git push no-mistakes

Infinitary checked this version: an independent review that also judged the documents, and live validation the review accepted.

@github-actions github-actions Bot added this to the 0.1.1 milestone Nov 14, 2026
@mremond
mremond force-pushed the fm/task-a9639ed2 branch 3 times, most recently from 260537a to 2140ddf Compare November 15, 2026 09:48
@mremond
mremond merged commit 6cd3afa into main Nov 15, 2026
21 checks passed
@mremond
mremond deleted the fm/task-a9639ed2 branch November 15, 2026 14:05
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.

1 participant