Skip to content

fix(runtime): preserve ETS tables for configured heirs - #50

Merged
mremond merged 2 commits into
mainfrom
fm/task-9d9adf9b
Nov 15, 2026
Merged

mremond merged 2 commits into
mainfrom
fm/task-9d9adf9b

Conversation

@mremond

@mremond mremond commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Why

Configured ETS heirs lost their tables and contents when the owner exited.

What changed

  • Live heirs recover table contents and ownership before exit notifications.
  • Heirs receive transfer messages with gift data that survives garbage collection.
  • Missing, dead and self heirs retain table-deletion behavior.

Before and after

Before: Both native scheduler modes received EXIT instead of the required transfer notification in the baseline regression.

After: Twenty native and ten reference runs demonstrate inheritance; the full native repeat passes 502 tests with two external-module skips.

This changes runtime ownership and message delivery, not a graphical interface; native and reference transcripts retain the observed table state.

Checked

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

Scenario Result Evidence
Native heir recovery ✅ Passed live Ten default and ten single-scheduler runs completed all assertions and both markers, recording 320 transfers per mode.
OTP reference behavior ✅ Passed live The unchanged fixture completed ten reference runs; independent review confirmed that these observations remain applicable.
Complete local project gate ✅ Passed live The full repeat passed 502 native tests; an earlier TCP timing failure remains unexplained, with other-workload concurrency unknown.
Deterministic ownership and ordering regressions (supplementary) ⏸ Supporting evidence Four new regressions passed ten rounds; the existing exit-order regression and complete workspace suite also passed.
  • Independent code and proof review: Accepted the implementation, lock-release repair, equivalent branch repair and refreshed validation beside the retained unexplained timing failure.
  • Publication scope review: The branch contains only heir support, its regressions and corresponding documentation; no dependencies changed.
  • Mergeability preflight: The reviewed version combines cleanly with the default branch without another branch update.
How it was checked

Built the runtime before the compiler with the pinned toolchain and locked dependencies.

Ran cargo clippy --workspace --all-targets --locked -- -D warnings and cargo test --workspace --locked --no-fail-fast; 2,196 Rust tests passed with one ignored measurement.

Ran ./target/release/nera test -j 1 --timeout 30 and the allocator, stacktrace and shutdown regression scripts.

The first full native suite observed a tcp_reactor_perf batch-variance failure; one full serial repeat passed using identical compiler, runtime and fixtures.

The original failure remains unexplained. Historical and repeat other-workload concurrency is unknown; no exclusive-host, host-load cause or flake claim is made.

The passing performance fixture prints no batch vectors or threshold margins. All 100 isolated runs on main and 100 on the change passed its thresholds, but did not reproduce the full-suite context.

All ten shutdown cases completed thirty samples; the largest median was 1.54 ms against the 5 ms limit, and the largest sample was 1.98 ms.

The shutdown gate checks medians, not maximum latency. The native baseline failed at the missing transfer while the unchanged reference fixture passed.

Risk

Risk above low: Blast radius, medium — Changes common process-exit cleanup and ETS ownership registry operations.; Novelty, medium — Adds owned heir gift storage beside existing table and message machinery.

Full risk assessment
Dimension Level Why
Blast radius medium Changes common process-exit cleanup and ETS ownership registry operations.
Behavior low Corrects ignored heir settings while retaining deletion when no live heir can inherit.
Undo low A revert restores prior runtime behavior without migrating persistent data.
Evidence low Repeated native and reference journeys and the accepted complete local gate demonstrate recovery.
Sensitivity low Touches in-memory tables, not credentials, payments or signing.
Novelty medium Adds owned heir gift storage beside existing table and message machinery.
Dependencies low No package or dependency changes.
Not done

Changing heirs with ets:setopts/2 remains unsupported; access-control behavior is unchanged.

Windows and target-native macOS x86_64/Linux arm64 execution were not performed.

The original TCP timing failure remains unexplained; concurrency and passing threshold margins remain unknown.

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 merged commit dbf156b into main Nov 15, 2026
21 checks passed
@mremond
mremond deleted the fm/task-9d9adf9b 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