Flake: nightly poetry hosted rollback fails on one transient PyPI request (UpstreamClient has no retry)
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- rust
- 领域
- networking, testing
调研方向
Start with crates/socket-patch-core/src/patch/redirect/upstream/client.rs and inspect get_json_authorized and download, then compare their error handling with api::client::network_error_detail and the retry behavior in api::retry and send_json_request. The reproduction is crates/socket-patch-cli/tests/e2e_vex_build/poetry.rs:898; first establish how to classify the transport error, then determine whether a bounded retry is warranted. Done means the cause is visible in errors and any retry policy is covered by relevant tests.
由索引模型根据 Issue 内容生成。
描述
Nightly e2e-extended (ubuntu-latest, e2e_vex_build, poetry:: --ignored, 1.1.15) failed once on a single failed PyPI request during hosted rollback.
Evidence
- Run https://github.com/SocketDev/socket-patch/actions/runs/39101574188 (schedule, main, 2026-10-18), job 117599202945
poetry::poetry_hosted_fresh_install_then_manifestless_vexpanicked atcrates/socket-patch-cli/tests/e2e_vex_build/poetry.rs:898:rollbackexited 1 withhosted_restore_refused:
cannot restore pkg:pypi/[email protected] to its upstream registry entry: six==1.16.0: GET https://pypi.org/pypi/six/1.16.0/json: error sending request for url (...)- The other 3 poetry tests in the same job reached PyPI fine seconds earlier. The 10-19 nightly passed on the same code.
- Frequency: 1 of the last 12 nightlies. It has not been seen on PR or merge_group runs (this leg is nightly-only).
Root cause (partly known)
UpstreamClient (crates/socket-patch-core/src/patch/redirect/upstream/client.rs) sends each registry lookup once. get_json_authorized and download turn any transport error into a final GET {url}: {e} with no retry. The patch API client does retry dropped connections and 429/503 (api::retry, send_json_request). Because the message keeps only reqwest's top-level text, the log can't tell us the transport error class (DNS, reset, timeout).
Proposed fix (not started: the evidence was too thin this run)
- Format registry-lookup errors with the cause chain, the same way
api::client::network_error_detaildoes, so the next occurrence is classifiable. - If it recurs as a dropped connection or a 429/503, give
UpstreamClient's GETs the same boundedApiRetrypolicy thatsend_json_requestuses (is_retryable_transportplusis_retryable_status, the shared retry window). A user's hosted rollback hits the same failure mode.
Filed by the hourly CI janitor; the job log expires, so the signature is quoted above.
Generated by Claude Code
- 主要语言
- Rust
- 星标
- 8
- 派生
- 1
- 平均合并
- 17 小时 56 分钟
- 30 天内合并 PR
- 594
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
SocketDev/socket-patch 的其他 Issue
-
agent:triaged bug bughunt pm:pipenv priority:p1
难度 2/5 1-3 小时 新手友好度 78/100
SocketDev/socket-patch#1608 · 1 条评论 ·
维护者通常 1 天内回复
-
agent:triaged bug bughunt pm:vlt priority:p1
难度 2/5 1-3 小时 新手友好度 62/100
SocketDev/socket-patch#1601 · 2 条评论 ·
维护者通常 1 天内回复
-
agent:triaged bug bughunt pm:npm priority:p3 ux
难度 2/5 1-3 小时 新手友好度 75/100
SocketDev/socket-patch#1072 · 2 条评论 ·
维护者通常 1 天内回复
-
agent:triaged bug bughunt pm:yarn-berry priority:p1
难度 2/5 1-3 小时 新手友好度 73/100
SocketDev/socket-patch#783 · 1 条评论 ·
维护者通常 1 天内回复
-
CI perf: floating toolchain versions in ci.yml e2e — upstream uv 0.13.2 red-mained the merge queue for 2.7 h (~4.3k job-min wasted on 10-20; ~0.45k min/day amortized)可能已有人在做 @mikolalysenko 于 1 天前认领。 未关闭agent:claimed agent:triaged ci-perf priority:p3
难度 4/5 3-5 天 新手友好度 35/100
SocketDev/socket-patch#1645 · 2 条评论 ·
维护者通常 1 天内回复
查看 SocketDev/socket-patch 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
git-ai-project/git-ai#2434 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
peteonrails/voxtype#909 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
kucherenko/jscpd#1239 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
alchemyplatform/rundler#1358 ·
维护者通常 3 天内回复