Repository navigation
mtcollins1 media: a listing naming the image twice is its own typed cause, with both identities (#12533 finding 5) - #12553
Closed
gunbai-bot[bot] wants to merge 51 commits into
Closed
gunbai-bot[bot] wants to merge 51 commits into
gunbai-bot[bot] wants to merge 51 commits into
Conversation
…model Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ote host, wall clock models Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…, remote request, coreutils formats, parent rule) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…tore), ipmitool observed-output rows, SOL collector/process table, SDR dump, SMpro, uptime, host console Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… the real entry (deadline refusal, pinned SOL-teardown defect, held-unit contender) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… each case's own cause; media withdrawal and SOL-drop events Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…UnimportedBareProvider on 'grant') Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…; wall clock on std.measure carriers; seed-growth row covers the file arm - Per eager-owl-205's ruling (msg_83af891b): the eleven matrix cases over the new-witness eval-step budget are typed cost-debt admissions (floor_cost_debt_admission mtcollins1_boot_matrix_typed_admissions, reason not reading) and members of a declared 4b(3) drop (gunbc.rung_drop mtcollins1_boot_matrix_new_witness_eval_step_cost, list floor_eval_step_cost_drop_boot_matrix_rows) whose restoration trigger is the natively emitted evaluation frame on the merge path. The two cases under the per-subject line are neither (a row there is stale). - Review 72230: ModeledWallClock carries EpochSecs and a signed std.measure SecondDisplacement (new, beside CelsiusDelta/ArcsecondDisplacement). - Seed-growth row names file_result_of_observation and the file/argv boundary. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Ledger-Repair-Judged: docs/design-rung-drops.md Ledger-Rows-Repaired: docs/design-rung-drops.md mtcollins1_boot_matrix_new_witness_eval_step_cost Heal-Candidate-Run: 36427507942
…e host's boot (one attempt), stale cost-debt rows removed, drop population = the 8 over-budget cases, rung-drop projection regenerated The first floor run showed every typed cost-debt row stale: the matrix cases sit under the 500ms per-subject line, where such a row blocks. The honest fix is cost, not a different exemption: operation_realization_index maps bindings by identity once per frame (each of ~190 dispatches no longer scans the list), and the SOL-loss case no longer pays a baseline attempt. Measured locally the dearest case is now 220ms CPU (was 307ms on CI), under the 302ms enrolment margin. OperationBoundTwice/BindingMatch deleted (unreachable: duplicates refuse at admission). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…e current authority Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…the total form) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…othing when nothing is due Measured on the deadline case (temporary instrumentation, reverted): the modeled dispatch was ~110ms of ~243ms CPU, and handler selection ~60ms of that -- the covering_grant fold re-derived per dispatch for ~15 distinct operations. The selection reads only the operation identity and readonly flag besides frame-fixed inputs, so the slot keeps each decided selection keyed by that complete identity. The world advance short-circuits when no BMC event, media transition or console line is due. Deadline case now 214ms local (was 307/284ms on CI runs). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ause with both identities, not invalid JSON (#12533 finding 5) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ps its SOL drop) #12423 side-chat review 5342387382: bmc_advance_pending rebuilt pending from its own accumulator after each applied event, discarding events the transition had just scheduled -- a power cycle's restore arming the after-boot SOL drop lost that drop. The advance now fires the earliest due event from the world's own pending list, applies it, and repeats on the world that transition produced. New model control a_power_restore_keeps_the_sol_drop_it_schedules (ON host, cycle at 0, restore at 5, drop at 35; quiet advances to 10 and to 40); it fails on the previous fold. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…entities (finding 5 flips) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
gunbai-bot
Bot
changed the base branch from
main
to
session/swift-deer-358-pr2
September 28, 2026 18:14
gunbai-bot
Bot
changed the base branch from
session/swift-deer-358-pr2
to
main
September 28, 2026 18:17
Contributor
Author
…e of UTF-8 bytes - Review 72311: a file operation dispatched without a string `path` is a harness fault, not an empty path fed to map_file_outputs. - Review 72309 (relayed from #12554): FileOperationSucceeded.byte_count is a std.measure ByteSize, and gunbc.filesystem_model fills it with the UTF-8 byte length (std.bytes utf8_encode_bytes, as std.materialization_object does), matching the realization's content.len(), not the code-point count. The dispatcher reads it through extdeps.transports.file file_observation_byte_count. Control: a_modeled_read_counts_utf8_bytes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
briansrls
enabled auto-merge
September 28, 2026 19:21
briansrls
added this pull request to the merge queue
Sep 28, 2026
briansrls
removed this pull request from the merge queue due to a manual request
Sep 29, 2026
…eNameRead) The refusal is main's latent defect in extdeps.systemd.journalctl, which read String through std.types (a re-export) and Unit bare; it surfaces in the claim scope this PR's touched modules select. journalctl is outside the stage0 closure, so std.string_type is admissible there (the earlier stage0 edge refusal was the calendar in iso8601, since moved). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ion (review 72549) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…usBareNameRead) Its Filesystem.Read/Write are the extdeps.filesystem.filesystem_io service; std.resources also declares the name. Main's latent defect, surfaced in the roadmap witness scope this PR edits. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Main conflict (after #12517/#12482/#12586 landed): the conflicting paths are |
…drop projection regenerated floor_eval_step_cost_drop keeps the boot-matrix rows and main's dark-install render rows side by side, and floor_eval_step_cost_drop_all_rows concatenates both. docs/design-rung-drops.md is regenerated by generated_artifact_gate main_wet over a build of the merged tree. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… session/nimble-raven-273
… hoist (review 72606) claim_batch: building the healthy world, its census console and the frame costs 1,687-3,793 eval steps against 78,317-119,267 per member; with it removed every member stays over 72,300. The world is already a supplied value, which is the witness rule's remedy, not a derivation. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…12602) #12602 made ArgvCommand.program a sealed ProgramIdentity, so the model's own `command.program as String` stopped yielding the program word and every matrix case refused at the ssh-add check on the queue's composed revision. The model now uses the production renderer extdeps.exec.command argv_words, the one authority for a command's words, rather than re-deriving them. docs/design-rung-drops.md regenerated. claim_batch: the matrix, the realization, model and filesystem witnesses, 42 of 42 PASS on the merged tree. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…trols The dry realization now answers the route #12434 landed: - processes carry a start time, visible as /proc/<pid>/stat (field 22) beside cmdline; ActivateHeld publishes "<pid> <starttime>", sends the grounded preamble's banner to the capture and its stderr to the client diagnostics, and a foreign session's refusal to the diagnostics; - one exit transition (deactivate, session drop, ReleaseHeld) removes the /proc entry and records the supervisor's exit line; ReleaseHeld stops only the recorded instance; - the notice watcher the step starts before the entry is scenario state (with_notice_watcher); - shell.Move File is a rename in gunbc.filesystem_model; ipmitool mc info answers with the two fields the corpus read from this controller, its layout typed TranscribedUncited. Flips: pinned_a_healthy_census_is_refused_at_the_sol_teardown -> a_healthy_census_completes_and_releases_its_collector (ok; deactivate, ReleaseHeld, two retiring deletes, all under the hold). pinned_a_sol_loss_mid_boot_is_reported_only_at_the_deadline -> a_sol_loss_mid_boot_is_reported_before_the_deadline (typed ObservationChannelLost, incident frozen, BMC answering, teardown within 60 s of power-on). The held-elsewhere case asserts the typed cause. claim_batch, the merged tree: matrix, realization, model and filesystem witnesses 42/42 PASS. The eval-step drop now covers nine members (the listing case crossed the budget on the longer route), each row re-measured; docs/design-rung-drops.md regenerated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… session/nimble-raven-273
…wer action and within 60 s At bd99cbb first_dispatch_second returned -1 when a dispatch was absent, so an absent teardown, or one before the power action, satisfied the delta bound (side-chat hold on #12533). Both instants are now Optional, the delay must exist and be nonnegative, and the route must carry exactly one SolDeactivate after the power action. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
CI at f42ca80:
#12533 is red on the same checks at bd99cbb. This PR's own case ( |
…red drop; two eval-step rows Side-chat ruling (eager-owl-205, 2026-09-30): the six cases CI measured strictly above the 302 ms enrolment margin and under the 500 ms line (396, 394, 378, 361, 339, 332 ms, run 36648847499) are rostered in v2.workflow.floor_enrolment_dead_band, self-staling both ways, under the declared drop gunbc.rung_drop.mtcollins1_boot_matrix_enrolment_dead_band_observed_only. Its population derives from those rows, and its trigger names the one capability both matrix drops wait on, now a single row (mtcollins1_boot_matrix_native_witness_capability) that the eval-step drop also reads. The CPU is #12434's own polling route run faithfully; ablation found no model hotspot. The eval-step drop gains the interrupted-attempt and wrong-share cases (74,419 and 77,423 on CI), eleven rows. Rung-drop and enrolment witnesses 19/19 PASS; docs/design-rung-drops.md regenerated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…solution for wet and modeled #12636 binds linux.Procfs ReadUptime to the file transport with its path as a literal in the transport, not an input. The modeled file arm read the path from the inputs, a second and narrower route to the fact the wet dispatch resolves from the transport, and refused every matrix case at the uptime read. file_transport_path is now the one resolution both arms use (rostered in gunbc.modeled_operation_realization_seed_growth), and the dry uptime handler answers FileObserved with the record's final newline, the byte #12636 exists to keep. Re-measured on the merged tree: 51/51 PASS. The interrupted-attempt case is back under 72,300 (70,000) and leaves the eval-step drop; ten rows, each at this tree. Rung-drop and enrolment witnesses 19/19; docs/design-rung-drops.md regenerated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… session/nimble-raven-273
Contributor
Author
|
Floor red at this head for the same reason as #12533: |
…ter as NotAReference The floor refused RosterStale: the file no longer carries the pair. measure.dag has imported Time from extdeps.units.iso_80000_3 since 2026-09-05, before the roster was seeded on 2026-09-25, so the file did not change; the seeding reader derived an imported name as unimported, and the parsed reader (#12609) does not. That is NotAReference -- the READER changed -- not ImportsFixed, which would claim a file change that did not happen. This PR surfaced it by touching measure.dag. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The floor's run 36661418914 measured it over 72,300 where a local claim_batch read 70,000; the floor's figure decides membership. Eleven rows; docs/design-rung-drops.md regenerated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… session/nimble-raven-273
…ration loop and presentation_still_served's enumerated arms; std_measure.rs takes both sides' additions Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
The floor refuses at compile: main's #12492 test |
Contributor
Author
|
Superseded by the integration PR #12800, at the operator's request; this branch is merged there unchanged at its current head. — sent from eager-owl-205 |
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
1 participant
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.
Finding 5 of #12533. §6b: the earliest unjustified boundary is
image_index_named. ItsImageIndexAmbiguous { count }dropped the identities of the matching rows, soimages_listing_readingcould only fold a well-formed listing intoImagesListingUnparseable, which was then reported as "not valid JSON".ImageIndexAmbiguous { image_indices }now carries every matching row's image_index. A matching row with no numeric index is still an unread member, as on the unique arm.ImagesListingOffersAmbiguously→MegaRacImageOfferedAmbiguously(fresh path) andEnumerationAmbiguous→MegaRacOfferedAmbiguouslyAfterDetach(after the refresh). The await loop refuses on it at once instead of feeding it to the mount standing as a miss.a_listing_naming_the_image_twice_is_ambiguous_not_first_matchnow asserts the identities. The newa_duplicate_listing_reports_both_identities_not_invalid_jsonfails against the old label.a_listing_that_names_the_image_twice_starts_nothing.Verification: the local witness run could not complete (the remote runner OOM-killed it while loading the corpus), so the CI floor is the first execution.
🤖 Generated with Claude Code