Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#299 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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
スター
2
フォーク
2
平均マージ
12時間 2分
マージ済み PR（30日）
60

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

tableau/hyper-api-rust のほかの issue

tableau/hyper-api-rust の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。