Repository navigation
Export bounded native PBT inputs and outcomes without point events - #588
Open
CaelmBleidd wants to merge 1 commit into
Open
CaelmBleidd wants to merge 1 commit into
CaelmBleidd wants to merge 1 commit into
Conversation
This was referenced Oct 16, 2026
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.
Long PBT comparisons need original inputs and outcomes after generation, but point observations retain at most 64 invocations and repeatedly serialize their whole history for byte accounting. Add an opt-in compact input export with the existing tagged snapshot, phase, admission and outcome types. It records no point events or execution trees, and does not create a session or restart generation.
Inputs are snapshotted before precondition/predicate mutation. The recorder accounts only each new record's bytes, reserves final admission/outcome and counter sizes, and preserves explicit count/byte omissions, unsupported snapshots and pending asynchronous outcomes. Publication copies terminal fields so a late callback cannot turn a pending receipt into a completed one. Source identities, count, byte bounds, arity and omission counters are validated at the actual Kotlin process boundary. The opt-in export is bounded by 100,000 records and 2 MiB, within the existing 4 MiB wire limit; coverage attaches through its existing separate collector and old observations retain their existing bound. A transport/serialization error remains an explicit backend failure.
The API adds optional
inputExportRequest/inputExportfields to the existing run configuration/result. Defaults retain the ordinary generation path and publish no input export. Overflow is evidence of incomplete capture, even when the original property run succeeds. This enables a later driver follow-up to use a large declared run quota and accountable budget stop; it does not itself establish an equal-budget experimental result.Stacked on #586 at
6e632337a9106fdfe84b29dc95c4356df864ed82. No path selector, README or generic spool framework is added.Validation: 218 Node adapter tests passed, including late-publication immutability and wire validation. All seven new real
FastCheckBackendtests passed: 300 records alongside coverage/old observations, a response above 1 MiB through the actual transport, UTF-16 and nested arrays, precondition/predicate mutation isolation, count/byte overflow, unsupported snapshots/pending async work, and disabled defaults. The 21 nearby existing backend/invocation tests also passed. Main/test Detekt for both PBT modules reports zero findings. The driver still requires explicit complete capture before primary class comparisons.