Repository navigation
验证:闭合工作区尺寸标记残尾回归 #63 - #93
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Oct 27, 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.
问题与结果
原 UI 窄布局第三轮停在 stage52,主区第三轮停在 stage7。实际子进程尺寸和原生标记已经正确,底部候选核心却在
TF_SIZE_169x11后保留旧 helper 路径,精确整行条件无法通过。本 PR 用同 EXE 单变量、原生快照、实际运输回放和无插桩回归核验现有 #51 native_viewport 修复覆盖两条路径,补齐 #63 的因果证据;没有新增产品/测试源码改动。主区场景的活动主会话两策略均得到
TF_SIZE_112x24,失败条件实际来自底部会话。旧策略按捕获 feed/resize 顺序回放逐字段等于同次 live core,新策略得到精确标记,避免仅凭一次绿将历史失败归因。固定身份与范围
基点
dd533878538490c2464673218ea0000c6467a495,HEADba9e7bd10596347c20dbbbc4d2c5e7cca600a0b3;候选 termforge.5 × 官方 ConPTY1.25.260930003 × flags24。旧原入口为188228e/.4固定EXE,两项原三轮各两绿一红;单窄UI仍原红。新源单变量两对分别用同一诊断EXE,保持原输入/布局/断言/20或30秒内层及40秒外层,各原红/绿一次,未重试取绿。原件、临时补丁、EXE、native cells和helper路径仅本地。公开白名单证据 SHA256为
8da8fc9078d9e31e14235f4a97574d18b670c87784495948735ea65463a939b6(Git及本地LF一致)。观测上限、未截断及停止条件有记录。探针影响调度,原生快照/末端/窗口呈现分列,不构成性能结论;更早缺运输样本不追溯认定同因。无插桩验证
临时四份C++已逐字节恢复并实际重建;固定产品源dd53387与c662011相同,最终EXE
7f26395942f107297565f50402568650e1e17c5eb23924bee1bfb02c50c60d16与诊断身份分列。shellCTest 93.62秒内完成(原180秒期限):40项中 37通过、3原hosted clipboard guard跳过。其中UI/main再各运行三轮,共18份相关样本Job active0/terminated0、desktopgone。git diff --check通过。Spec/Standards两项独立审查均无发现;已复核原件哈希、三条回放、原生屏幕、18份正式样本、几何/像素与原期限。首次CI失败已保留,见下方分项结果。仅合入实验父分支
fix/conpty-backend-r47。拟按限定合同完成 #63;#52 Vim、#47完整官方矩阵及R2仍开放,Draft #50不合入main。没有把本次shell结果拼成完整57项验收。Refs #63, #47, #35。
CI 与保留失败
同HEAD、同实际checkout
5cd12da8c4cbded082e7686a2b8db91c7b9e9f2f的配置分别记录:d0150af666d84b2fb26648fd978b18d2f85de657a50c72644db32785bc0ca2c7已核对。ui-copy-system原两轮各12基础阶段/28交互阶段、真实复制和占用恢复通过,离线原validator再次通过;两例exit0、非超时、Job active0/terminated0、desktopgone。复查是本纯文档/证据PR的集成结果,不证明#73已修复;#73保留开放和首轮失败。#63官方配置的因果及无插桩验收与此默认/system结果分列,拟仅合入实验父分支;#52/#47及Draft #50仍未验收。