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

hyperdb-bootstrap never prunes superseded hyperd pins (793 MB for one active version)

未关闭
  • 哪里不对？
#299 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
powershell, rust
领域
build-system, tooling

调研方向

Start at hyperdb-bootstrap, especially download_and_extract and refresh_current, then inspect the make clean target and build.ps1 equivalent. Clarify whether cleanup should retain one previous pin or only the active pin, and verify that installation and targeted cleanup remove stale versioned directories while preserving current/ and the active release.

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

描述

Summary

hyperdb-bootstrap never removes a superseded hyperd release, so every pin bump leaves the previous one on disk permanently. On this workstation that is already 793 MB for a single pinned version:

263M	.hyperd/0.0.26359.r07abb490    <- superseded pin, nothing references it
265M	.hyperd/0.0.26479.r96880f6a    <- the current pin
265M	.hyperd/current                 <- a full copy of the current pin
793M	.hyperd

Two things compound:

  1. No pruning on bump. download_and_extract clears only the directory for the release it is installing, and refresh_current clears only current/. Neither considers older versioned directories, so each bump adds ~263 MB that is never reclaimed.
  2. current/ is a full file copy rather than a symlink. That is deliberate — it avoids requiring symlink privileges on Windows — but it means the active pin is always stored twice.

Nothing in the repository references the superseded directory by path; the only 26359 matches are version strings in changelogs, benchmark history, and a --version example.

Why the existing cleanup does not help

make clean does rm -rf .hyperd, which removes current/ along with everything else and forces a full re-download of the pinned release. So the only available cleanup is all-or-nothing: either carry the superseded copies indefinitely, or discard the working engine too and re-fetch ~265 MB.

There is no targeted way to say "keep the current pin, drop the rest."

Fix direction

Either would resolve it, and they compose:

  1. Prune on install. After refresh_current succeeds, remove versioned directories under .hyperd/ other than the one just installed. Doing it after the new pin is verified and current/ is refreshed keeps the operation safe — a failed download must not leave the tree with no usable engine.
  2. Add a targeted cleanup target. A make clean-hyperd-stale (plus the build.ps1 equivalent) that removes superseded versioned directories while leaving current/ and the active pin intact. Useful independently of (1), since it also cleans up trees that predate the change.

Worth considering whether to keep exactly one previous pin, which would make an A/B benchmark against the prior release — the procedure the update-hyperd-release skill documents — possible without re-downloading. That argues for pruning to N most recent rather than to one.

Provenance

Noticed while correcting the HYPERD_PATH guidance (#298). Verified against main at 05e993f.

主要语言
Rust
星标
3
派生
2
平均合并
23 小时 11 分钟
30 天内合并 PR
65

环境准备

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

从这里开始

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

tableau/hyper-api-rust 的其他 Issue

查看 tableau/hyper-api-rust 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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