Reject engine clock and event-ID exhaustion before authority mutations #630
No reviewers
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erikinkinen/AES!630
Loading…
Reference in a new issue
No description provided.
Delete branch "phase2/bug-629-engine-overflow-guards"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task
Closes #629.
Summary
An event at the maximum logical clock previously created authority and wrapped
time to zero. An exhausted event-ID cursor reached a fatal generator assertion
after applying the graph operation. Both engine entry points now return
Errc::Overflowbefore dispatch, preserving graph, history, cursors and meters.Scope
Adds one preflight capacity guard and boundary regression fixtures. Direct
ID-generator behavior and valid legacy event behavior remain unchanged.
The research intent transaction remains separate work in the version-4 path.
Design intent
Reject exhausted infrastructure capacity before a mechanism performs any work.
The last legal clock/event identity succeeds; the next attempted mutation fails
without adding or clearing work. IDs a caller allocated before
stepremainoutside the entry point's preflight boundary.
Phase discipline
The fix applies to both original and measured entry points and supports the
research hard-error/no-mutation contract without changing legacy success cases.
Verification
Before the fix, the clock probe printed
error=0 time=0 authority_created=1 events_added=1; the event-ID probe exitedwith SIGABRT. The new CTest failed on the original code with the expected
Overflow assertion. With the fix, all 57 tests pass at source commit
5bc3ad8780in Debug, Release and Clang ASan/UBSan.Fixtures cover each limit separately and together, both entry points, preserved
nonempty meters, and the final legal event followed by rejected deletion.
The archived legacy cases and repository hooks pass.
Before/after logs, reproducer, JUnit and toolchain evidence.
All eight final-head Forgejo checks must pass before the three issue steps are
checked once and the PR is merged.