Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Improve the performance of the tool-versions version resolution

未关闭
#7,908 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, typescript

调研方向

Start by reading the changes in #7825 and #7826, then inspect the tool-versions resolution paths and the follow-ups to #7887. Measure which resolution paths and parsing costs affect actual install-tool requests before choosing an optimization; done means reducing unnecessary resolution cost while preserving fresh releases and the documented fallback behavior.

由索引模型根据 Issue 内容生成。

描述

What would you like containerbase to do?

Keep the version resolution through the tool-versions data cheap, as hosted Renovate runs install-tool millions of times a day and every run starts without a cache.

Costs per run since #7825 and #7826, for tools without their own resolver (exact versions read nothing):

  • latest or a missing version: one HTTP request to the online tool-versions data, tens to hundreds of ms, up to the 30 s timeout when the network stalls, plus an embedded read as fallback
  • a partial version: one embedded read and parse, plus the HTTP request unless the embedded data lists the version
  • an embedded read: JSON.parse and the zod check of one <tool>.json, below 0.5 ms typical, ~8 ms for the largest file (renovate.json)

Ideas

  • skip the online lookup when the embedded data is recent enough, needs the release time of the data (containerbase/tool-versions#149)
  • measure the zod check at runtime again and drop it if it matters (the image build already checks the data)
  • check which versions Renovate requests from install-tool (exact, partial or latest) to know which paths matter
  • measure the cost of the follow-ups of #7887 once more tools resolve through the data
  • any cache of the online data that outlives one resolve (per process, or on disk like HttpService.download()) needs an expiry time, so long running processes pick up new releases; today getJson() doesn't cache and the ToolVersionsService cache only lasts one resolve
  • warn when the v1 format is deprecated (with its removalDate) in the root index.json; the online lookup fetches v1/<tool>.json directly and after a removal would silently fall back to the embedded data on the 404. Not on every run, eg. only after a 404 or at most once a day

Drafted by Claude Opus 5.5 (Claude Code) for @viceice.

主要语言
TypeScript
星标
58
派生
65
平均合并
11 小时 54 分钟
30 天内合并 PR
428

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

containerbase/base 的其他 Issue

查看 containerbase/base 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。