promote: a pool lecture renamed or removed upstream can never be retired, and every refresh after it fails
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 58/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- python
- 領域
- build-system, tooling
調査の方向性
Read tools/drift-check around the canonical-removed finding and tools/promote around refresh failures and the generated ledger. Trace how lecture entries and their assets are recorded, then inspect the existing promotion tests. Add coverage for renames, removals, and assets used only by a retired lecture; done means a supported retirement workflow clears drift and later refreshes succeed.
索引モデルが issue の本文から書いたものです。
説明
Found by the review of intro's promotion for step 2 of QuantEcon/project-monorepo#24. The gap predates that promotion, but each series promoted widens it: intro adds 50 lectures to the pool, and intro changed its _toc.yml 11 times in the last six months. Line numbers are at main 83f0179.
What happens. Reproduced on a copy of the pool with intro promoted, by renaming intro's cobweb.md to cobweb_intro.md in its mirror and its toc and moving intro's pin:
tools/drift-checkreports two drift findings:[toc-changed] introand[canonical-removed] lectures/cobweb.md: canonical copy intro/lectures/cobweb.md no longer exists upstream.- The
toc-changedremedy (tools/promote --toc intro --exclude jax, thentools/drift-check --accept-toc intro) promotescobweb_intro, but leaveslectures/cobweb.mdand its ledger entry in place at the old pin, so the pool holds both. - The next night that any intro lecture moves (here
solow, with the pin moved again), the workflow's refresh (tools/promote --refresh --exclude jax) fails on the old entry and exits 1, so the run is red:[cobweb] FAILED: cobweb.md is in the pool, but no canonical-eligible series this run considers holds it any more (removed or renamed upstream?). - It fails the same way every night after that.
Why nothing clears it. canonical-removed asks for a decision "before the next refresh" (tools/drift-check:322), and the refresh's FAILED line asks for the same one (tools/promote:677-680), but no tool carries the decision out. Nothing removes a pool lecture together with its ledger entry, and the ledger's header says it is generated and must not be hand-edited (tools/promote:146). The toc-changed remedy text (tools/drift-check:583-589) does not mention the old entry.
Removing lectures/cobweb.md and its ledger block by hand, in one commit, does clear it: drift-check is clean and the next refresh succeeds. But that is the hand edit the header forbids, and a lecture with assets of its own would need their records removed as well.
What a fix needs. A sanctioned way to retire an entry: remove the pool lecture, its ledger entry and any asset only it uses. Two shapes, not exclusive:
- an explicit
tools/promote --retire <lecture>, which thecanonical-removeddetail and the FAILED line then name; - a
--tocrun that retires the entries whose lecture has left the toc and whose canonical copy is gone, which also makes thetoc-changedremedy complete for a rename.
Either way, with tests for a rename, a removal, and a retired lecture's own assets.
- 主要言語
- Python
- スター
- 1
- フォーク
- 0
- 平均マージ
- 1日 3時間
- マージ済み PR(30日)
- 17
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
QuantEcon/lectures のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
drift
難易度 2/5 1〜3時間 初心者へのやさしさ 35/100
メンテナーはふだん 1 日以内に返信
-
question
難易度 4/5 1〜2日 初心者へのやさしさ 44/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 4/5 3〜5日 初心者へのやさしさ 54/100
QuantEcon/lectures#24 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
QuantEcon/lectures の issue をすべて見る
似ている issue
-
area: providers/aws priority: p2 size: S type: bug type: testing
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
finos/open-resource-broker#851 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100
sandialabs/atlas-ui-3#1196 ·
メンテナーはふだん 1 日以内に返信
-
enhancement triage
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
ShaftHQ/SHAFT_ENGINE#7902 ·
メンテナーはふだん 1 日以内に返信
-
[Bug]: GraphML export writes invalid XML when a value contains a control character (e.g. form feed)オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
topoteretes/cognee#6646 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 75/100
DOI-USGS/pywatershed#428 ·