Skip to content

test: retain selection clipboard failure boundaries (#85) - #86

Merged
JavaZeroo merged 3 commits into
diagnose/hosted-preflight-r81from
diagnose/clipboard-boundary-r85
Oct 26, 2026
Merged

JavaZeroo merged 3 commits into
diagnose/hosted-preflight-r81from
diagnose/clipboard-boundary-r85

Conversation

@JavaZeroo

@JavaZeroo JavaZeroo commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

PR83 的真实系统选择复制在 forward/reverse 后返回 OpenClipboard:5,原记录无法区分 sentinel 写入和独立读回。本变更只在夹具原调用失败后记录阶段、调用目的、原错误码,以及打开窗口/数据所有者的安全类别;明确查询非原子,缺失诊断不会替换原错误。

增加默认关闭、仅既有 disposable hosted guard 允许的两项真实自有 owner 占用控制:stage6 写、stage7 读。通过原 execute/queued快捷键/真实CF入口校验原错误和释放、Job/桌面回收;原九阶段、两轮、30s/40s、精确字节及产品重试反馈不变。清理异常另记固定诊断并保留主异常,纯回归覆盖清理/诊断流各成功或失败。

验证:

  • 固定代码 0774d33b82745444e5629d14c758a09e2dd562bf:本地 default/system 定向2/2、3.57s;完整46/46、285.53s,13个内部skip分列,selection模块8pass/2真实CFskip。
  • 清理边界使用同一最终测试源码,抽取原无保护顺序真实exit1,修后4组合通过;不宣称复现原hosted占用原因。早期地址断言不可靠,已排除;首次缺声明依赖的41/46保留。
  • Standards/Spec代码和公开证据已审查;观测合同与固定记录保留原artifact、来源、未知和全部跳过。真实 hosted 验证如下。
  • 文档同步#53限定闭合并已合入实验父分支;本PR代码仍为默认/system分支,不引入实验后端。

子PR基于#83。原#85故障根因仍未知,#85保持开放;此处是观测和控制验证,不能算原故障修复、candidate/official完整矩阵或WindTerm性能验收。

Build40384977348,HEAD f057060c685888702b7c9b95942534361b6f0d17、checkout e98466a5bce9747858e2bbd18c01f4c68747f779:Windows default/system 46/46、270.69s,Ubuntu通过;External candidate40384977349 独立通过。artifact12680781542(4356796B,SHA256 479067d783b1cd0a10a30775e77582545adc189e23a19472c18523967dcf01e8)已核对。

两项实际受控调用分别得到stage6 sentinel-write、stage7 readback 的 OpenClipboard5/exit2,两类别均为same-process-window;owner release/线程退出成立、所有error为0。原system两轮和data-only两轮均完成9阶段/exit0;六例均非超时、Job active0/total11/terminated0、desktopgone。离线复核只读取已收集记录,未伪造hosted环境。原事件的操作与根因仍未知,保持#85开放。

@JavaZeroo
JavaZeroo marked this pull request as ready for review October 26, 2026 19:25
@JavaZeroo
JavaZeroo merged commit dfff1b0 into diagnose/hosted-preflight-r81 Oct 26, 2026
8 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 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-26T19:26:39.659640Z f057060 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