ITADN

Git Panel History stays stale after converting a shallow clone to a full clone

#62523Opentodayim 创建于 10 天前
area:integrations/gitplatform:remotestate:reproduciblereach:some usersseverity:S3
T
todayimcommented
### Reproduction steps 1. On a Linux machine, create a shallow clone of a repository with more than one commit: ```bash git clone --depth 1 https://github.com/llm-d/llm-d-batch-gateway.git ``` 2. Open the repository from Zed on Windows using Remote SSH. 3. Open the Git Panel and select the **History** tab. It shows the single commit available in the shallow clone. 4. In Zed's remote terminal, convert the repository to a full clone: ```bash git fetch --unshallow --tags git rev-parse --is-shallow-repository # false git rev-list --count HEAD # 407 ``` 5. Open Zed's Git Graph. The graph correctly displays the full commit history. 6. Return to the Git Panel's **History** tab. Restarting the Git Panel or switching projects does not make the newly fetched history appear. This looks related to, but is a more specific reproducible case than #13176. ### Current vs. Expected behavior **Current behavior:** Git Graph immediately shows the complete history after `git fetch --unshallow --tags`, but the Git Panel's History tab remains cached at the original shallow-clone state and shows only the one commit that was present when the project was opened. **Expected behavior:** The Git Panel History tab should refresh after the repository becomes a full clone and show the same commit history that Git Graph and `git log` show. ### Zed version and system specs Zed: v1.14.2 (stable 02abf5b08fa12c1c20a155ae3f796ef4c6c1a01e) Host OS: Windows 11 10.0.26200 (build 26200) Host memory: 31.5 GiB Host architecture: x86_64 Remote environment: Ubuntu 24.04.3 LTS, x86_64, connected via Zed Remote SSH Remote Git: 2.43.0 ### Attach Zed log file Not attached. No error is displayed; the History view remains stale. ### Relevant Zed settings No Git-specific settings. ### Relevant Keymap Default keymap. ### (for AI issues) Model provider details Not applicable. ### If you are using WSL on Windows, what flavor of Linux are you using? Not using WSL. The Linux environment is a VM accessed with Zed Remote SSH.
2 条评论