Repository navigation
Integrate PR869 and PR901 on current main with runtime qualification failures - #998
flip-baton-deepseek[bot] wants to merge 15 commits into
Conversation
…ain-integration-20261020 # Conflicts: # bend2/test/observer-monitor.py
…ain-integration-20261020 # Conflicts: # bend2/test/observer-monitor.py
…869-pr901-current-main-integration-20261021
…869-pr901-current-main-integration-20261021 # Conflicts: # bend2/test/observer-monitor.py
Classify large Codex spans from a bounded prefix, preserve small spans through the text path, and commit the checkpoint cursor for every consumed span. Add the rationale and unverified limits.
The candidate and target checks of the previous head failed in prepare-native-compiler.py with 'Unknown compiler archive SHA256': the branch's verifier did not list the pinned compiler archive 6609a2de that main now lists. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Root source review is complete. Current main contains this work through merged PR #1088 (
This older proposal is superseded by the integrated source. Its truncated JSON-prefix classifier can reject valid escaped input at byte4096 and must remain superseded. Root is closing #1047, #998, #869 and #901 on this source disposition. Replay-throughput work remains open in #1046; exact current-package runtime qualification and installed wake/chat-injection proof remain separate work in #1054 and the active critical package assignment. Closing these obsolete PRs does not claim those delivery results. |
Combined integration of PR869 and PR901 on current main
c021089a.Source identity
942b6075c437b0eea831350a4e15f75f30a3b9dfb8719c5af625ac2919ce15e846da952c5551aa9d2633af5bc(PR869 merge),b9e52ffcb(PR901 merge)c021089a622ccd278443cad3296c2328500c3fd8PR869 integrated head
e04afc534merged clean. PR901 integrated headb9e52ffcbmerged with oneobserver-monitor.pyconflict. The resolution keeps both test sets and onestart_attemptthat supportsharness,stdout_file,later_stdout_file,stdout_fixtureandspool_timeout. Theturn.benddelta againstc021089ais PR869's 173-line source change.Check-only
Bend 2.0.25 (
2.0.25-f5185e38-pr967-pr968-e5c4efd-20261019) check-only on942b6075c:bend2/src/coordinator/main.bend: exit 0, 34 unsafe/foreign definitions reportedbend2/test/monitor-fixture.bend: exit 0, 10 unsafe/foreign definitions reportedbend2/test/observer-recovery-entry.bend: exit 0, 4 unsafe/foreign definitions reportedCanonical queue build
/var/tmp/baton2-compile-queue/compile-queue-runner, state root/var/tmp/baton2-compile-queue, queue ownercompiler-queue-970-coordinator-20261019, compiler2.0.25-f5185e38-pr967-pr968-e5c4efd-20261019, CC/usr/bin/clang-19, linker/usr/bin/ld. Artifacts and receipts are under.scratch/pr869-pr901-942b6075c/.bdcf222c2cd6fa5ffae18089036779bb33caaa15e821da31ce6f89f357d9d4afobserver-recovery.c17,054,625 bytes, sha256a10fa6601b742ede55460c181e568af78d0e750ff90a32e29c23cd17dafa6939d72ba99f0624259909a961f417bbe714a734b628bffe84e5787cd5c6de3882dbmonitor-fixture.c858,819 bytes, sha2566be85be25b8de1b54a4998203c758bec8c9267d60a6b9a5e51948d608473e32267ade17670941d9173f4ba37e7870dc6a37da80effb75d8fe943e031d5d545c1observer-recovery8,199,248 bytes, sha256ba9dd3f52615a34b8b3a7f4aa1333bedd4f562427356519ea1ce018cc9e769c63fa6031ad7495b095a8c61e5e9fcca6f62dfdfaed4bb52a92b6c31198d14c8c3monitor-fixture1,421,536 bytes, sha2569703c04c449e669898957e2d5c4dd992a8e6d71cfd6a2d764044b1f3779c9c55The queue receipts record
status=completed,reused=0,verified=1,exit=0. The recovery Cgen ran for about 53 minutes behind the shared heavy lock. The fixture Cgen ran sequentially after it, not in parallel. The running issue937 keyf84471cewas not duplicated.Qualification results
The exact binaries were run with
OBSERVER_MONITOR_FIXTUREandOBSERVER_RECOVERY_BINset to the artifacts above, andBATON_MONITOR_REPLAY_SPOOL_FIXTURE=/mnt/nvme4tb/ci-runners/baton2-native-homelab/retained/recovery-output-fixture-20261018/stdout.bin(46,123,112 bytes, sha25687020b044a82014a8a4ef8166249be7a6012986f8f232c3868887f09bb521772).Preserved failures:
test_codex_large_assistant_frame_stays_spanned_through_report: FAIL,checkpoint_offset 0 != 8388608.test_codex_large_failed_terminal_stays_spanned_through_report: FAIL,checkpoint_offset 0 != 8388608.test_codex_large_failed_terminal_replaces_legacy_checkpoint: FAIL, the first checkpoint containscodex-span-v1with a span token for the 103-byte legacy line; the test expects the raw legacy assistant line.test_protected_spool_replays_to_normal_eof_with_unknown_monitor_custody: FAIL,checkpoint_offset 13598 != 46123112; the helper returned nonzero. The spool is complete at 46,123,112 bytes and the materialized native log is 76,399 bytes.observer-monitor.pysuite: 10 tests, 8 failures, 2 errors. Current-main tests also fail:test_spanned_agent_end_monitor_keeps_unknown_custodyreportsOperation not permitted;test_quiet_spool_awake_span_wakes_for_delayed_stdoutandtest_refused_resume_text_stays_an_incomplete_observationtime out;test_concurrent_observers_advance_the_cursor_once,test_fframes_absent_native_partial_output_preserves_unknown_custodyandtest_unknown_status_monitor_advances_once_and_keeps_owed_inputleave the cursor at 0.The retained attempt in each failure contains
checkpoint-error=state rejected by the observer; replaying from the beginning. The helper process waits inselect/pollwithout committing the large frame. The legacy test's first checkpoint is already acodex-span-v1token for the small legacy line.The result/event/report, native UUID and custody assertions after the failing checkpoints were not reached. The PR869 8MiB assistant and failed-terminal paths, the legacy checkpoint reopen, and the PR901 46,123,112-byte normal-EOF replay are not qualified by this head.
Rejected legacy evidence
The prior
788 b806/3fe6380dbuild with binaryad9ee93a...is retained as PR835 legacy-reopen evidence only. It lacksCodexSpanStateand was not used. Supporting records:knowledge-record:ece4dd7553241bd57b92f36db76c5af0andreport:f9c46045e4b33a33a46683aa6d47fa8e.Remaining gaps
The source at
942b6075cdoes not pass the required PR869 and PR901 runtime proof. The failing checkpoints prevent the exact result/event/report and cursor/native/custody assertions. This head is frozen for the recorded build; no source fix is included.