Repository navigation
fix(ios): consume bounded live events without dropping delta fragments - #277
Merged
Merged
Conversation
p697
force-pushed
the
codex/native-runtime-live-buffer
branch
from
October 16, 2026 13:03
d5d2e6a to
6d2fd82
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
2 participants
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.
Rapid live fragments could exhaust the native presentation stream’s fixed 64 slots while the main actor was still rendering. Keep the public AsyncThrowingStream and the 64-entry/16MiB limits, but pull from one bounded queue and concatenate only adjacent pure deltas with identical internal revisions and byte-exact route, segment and lineage. Every other event remains a barrier; all original weights count, real overflow still retires, and no write is replayed.
Validation: 14 new Swift test methods (15 parameter inputs), including actual Hermes/Pi mapper → coordinator → public stream with a paused consumer; existing SessionLifecycle (5 methods/11 inputs) and RuntimeOperations (6/12) passed individually with Swift 6/jobs2. Documentation checks: 16 instruction pairs and 7 regressions. Independent read-only review of head 6d2fd82 found no new blocker in cancellation/termination, lifecycle, bounds, scope ownership or the actual-mapper test boundary; all 13 checks passed on this exact current-main head before squash merge 6f1e623. CI executed 479 package tests (59 XCTest + 420 Swift Testing) and 315 native App tests with zero failures; the compiled resource check verified 19 locales, 2 tables and 9,082 exact values. Local strict Swift 6/iOS 16.4 development App compilation succeeded for both Simulator architectures, and its signature was verified. A protected QA development copy was handed off separately; no local full suite or device acceptance is claimed.
This is native iOS experiment code only; React Native remains the default. Actual debugging observed the host event-stream catch and later activate breakpoint, but stale PCM prevented sampling the failure enum or count-vs-weight subtype. This change is not proof of the complete original incident cause, successful actual Stop, or capacity-state recovery in the host. Cross-tool aggregate-final semantics remain a separate known limitation. No service/configuration, account, approval, distribution or release action.