fix(repository-workflow): 避免读取模型时抢占活跃 thread - #96
Merged
Conversation
Assisted-by: Codex:gpt-5.6-sol
Assisted-by: Codex:gpt-5.6-sol
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.
Why
Codex 引入 thread 单 writer 约束后，提交辅助脚本通过
thread/resume查询当前模型会与正在运行的主 App Server 争抢 writer lock，导致提交流程报错中断。What
thread/read获取 rollout 路径，并从最后一条完整的turn_context解析实际模型，避免恢复和抢占活跃 thread。CODEX_MODEL_NAME显式覆盖模型名。Validation
在仍由主 App Server 持有 writer 的当前 thread 中直接执行脚本，可以正常返回
Codex:gpt-5.6-sol，不再出现 active writer 冲突。Notes
PR 创建后仓库的全局依赖门禁检测到 Typer 最新版本已更新至
0.27.1；已通过仓库自带的依赖升级工具同步 18 个 uv 脚本的最低版本声明。