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

explorer: a restored snapshot loses to a folder's running animation

オープン
#305 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
zig
領域
desktop, testing

調査の方向性

Start with core/widgets/TreeWidget.zig (the branch's expanded and the _expanded data around lines 468 and 890) and plugins/workbench/src/files.zig (carryBack and the expander near line 1150), then find where setExplorerBranchOpen is called. Replay #293's property test with seed 0x6 to reproduce the failure. Done when the tree draws open or closed from the caller's value each frame, the expander reports toggles instead of writing back, and both the seed test and a new test that sets open state mid-close-animation pass.

索引モデルが issue の本文から書いたものです。

説明

bug

Found by #293 (#280 step B1), whose property test replays a demo and seeks to random moments. With seed 0x6 it fails in the tour's explorer, on seeks to 46937, 13890 and 17830 ms: after a snapshot restore, the explorer's open folders aren't the ones the snapshot holds. The checked-in seed and nine others pass, so this shows up only when a seek lands during a folder's open or close animation.

Cause: open state lives in two places that copy each other

  • core.widgets.TreeWidget's branch keeps its own expanded, stored per widget as _expanded in dvui's data (core/widgets/TreeWidget.zig:468, :890). It eases toward the caller's value through an animation.
  • The workbench keeps the explorer's open folders on the host (setExplorerBranchOpen, the per-branch open state the snapshot captures and restores). Each frame it writes the branch's expanded back into that state (plugins/workbench/src/files.zig, carryBack and the expander around :1150).

So a restore that sets the host's open state while a branch's own animation is still running loses: the next frame copies the widget's in-flight value back over the restored one. Nothing is wrong with the snapshot or the player. The model has two writers.

Fix

Give the open state one owner. The tree should draw open or closed from the caller's value each frame, keeping only the animation's progress as its own state, and never write it back. Clicking the expander reports a toggle to the caller, which changes its state. Then a restore, or anything else that sets the open folders (a reveal-in-explorer, a demo keyframe), takes effect on the next frame with no race.

Test: #293's property test with seed 0x6 must pass, plus a focused integration test: start a folder's close animation, set the open state from outside, run frames, and check the branch ends open.

Part of #280.

🤖 Generated with Claude Code

主要言語
Zig
スター
1.5k
フォーク
40
平均マージ
5時間 32分
マージ済み PR(30日)
537

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

fizzyedit/fizzy のほかの issue

fizzyedit/fizzy の issue をすべて見る

似ている issue

Desktop Dev の issue をもっと見る

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

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