Skip to content

[R2] 记录 hosted 准备收尾后的输出边界 - #159

Merged
JavaZeroo merged 4 commits into
mainfrom
diagnose/hosted-output-boundary-r2
Oct 28, 2026
Merged

JavaZeroo merged 4 commits into
mainfrom
diagnose/hosted-output-boundary-r2

Conversation

@JavaZeroo

@JavaZeroo JavaZeroo commented Oct 28, 2026 •

Copy link
Copy Markdown
Owner

hosted PS5.1 的既有10秒超时只记录 invoking/timed_out,无法区分是否捕获过命令正文marker。本改动在worker已reap且自有Job最终清空可验证后,读取固定白名单私有流,仅发布有界字节计数和完整ASCII marker行的true/false/null;缺失、超限、读错、不稳定和写入者未验证保持unknown。没有marker定义的命令明确not_applicable。

原命令、顺序、marker oracle、schema及命令/worker预算保持;新观测失败不覆盖原成功、command_deadline、worker_deadline或cleanup失败。真实文件seam红例 39921c1 在fake subprocess向实际stdout写marker再TimeoutExpired后缺少后验字段;d63be02补齐,测试源 87deb48 普通/-O相关纯/mock回归各32/32、0skip(新增10项)。正常/非0/worker期限、严格oracle拒绝额外私密行、65536/65537边界及读中实际变更均覆盖。

观测合同 · 脱敏验证身份。9个原命令/worker/guard/oracle函数及schema/budget对照未变,旧PR150/153的8份CI原件前后不变;公开不含输出原文、路径、PID或异常字符串。

本地只执行纯/mock测试,没有hosted setup、PS/WSL或真实Job API进程;没有新真实deadline观测。marker是收尾后的捕获事实,不证明截止前就绪;旧marker和旧根因继续未知,未重跑旧jobs。

发布HEAD eca88d280233a817cbb5ec63f4d2dcb21816487b。最终Standards硬违规/heuristic0、Spec P1/P2 0;本HEAD默认/Qt/参考的PR与push六工作流均success、attempt1。PR默认Windows59/59、288.20s/Linux39/39、15.98s(checkout b835369)。实际hosted5步骤全部通过,新输出观测覆盖10命令/20流:PS51 stdout29B、stderr0、完整marker=true;下载步骤not_applicable,WSL等无定义marker保持null。artifact12853669829(1420B)SHAc11bdc9c34571bc1ed009a1965c34c3aa1c0d4714dc0007aa41bdc14b5dfd315已下载核对。这是正常路径实证,没有新的真实deadline,旧#81原因仍unknown。准备按#158观测工具范围合入,#81/#38继续开放。Refs #158, #81, #38。

@JavaZeroo
JavaZeroo marked this pull request as ready for review October 28, 2026 22:17
@JavaZeroo
JavaZeroo merged commit 7de84de into main Oct 28, 2026
10 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-28T22:18:20.961273Z eca88d2 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant