Repository navigation
fix(runtime): stop immediately on fatal self-exit signals - #46
Merged
Merged
Conversation
mremond
force-pushed
the
fm/task-a9639ed2
branch
3 times, most recently
from
November 15, 2026 09:48
260537a to
2140ddf
Compare
Keep a normal self-signal sent while trapping nonfatal if trapping is disabled before delivery. Carry the suicide-request bit per signal instead of inferring it from sender identity during the mailbox scan.
mremond
force-pushed
the
fm/task-a9639ed2
branch
from
November 15, 2026 10:22
2140ddf to
bd0ae8f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A native process could continue after a fatal self-exit and report a later error instead.
What changed
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.
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
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.