vp staged reports a saved recovery patch that is missing after restore failure on Windows
维护者通常 1 天内回复
评估
调研方向
Start by locating the vp staged recovery path that emits “Failed to restore unstaged changes!” and writes unstaged.patch; the issue does not name a file or test. Reproduce the restore failure on Windows in a Git worktree, then inspect whether recovery leaves a durable patch or has already restored the changes. Done means the message accurately reports a patch that remains available or confirms recovery succeeded; pull request #3357 is already open.
由索引模型根据 Issue 内容生成。
描述
[!NOTE]
🤖 gpt-6.1-sol responding on behalf of Elliot
On Windows, a pre-commit hook running vp staged completed fmt, lint, and knip, then failed while restoring an unstaged formatting-only change:
Failed to restore unstaged changes!
Done reverting to original state!
Unstaged changes have been kept back in a patch file:
<git-worktree-dir>/lint-staged/<id>/unstaged.patch
pre-commit script failed (code 1)
Immediately afterward, the reported patch path did not exist. The staged source changes were intact and git diff showed no unstaged diff. This happened in a Git worktree after formatting an import change before committing; another changed-file validation command was also running. I have not isolated whether that concurrent validation contributed.
Please ensure the recovery message names a durable patch that remains available, or explicitly report that recovery already succeeded and no patch remains. A missing patch after a failed-restore message makes it hard to establish whether changes were preserved. No private paths or source data are included here.
- 主要语言
- Rust
- 星标
- 6.5k
- 派生
- 297
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 249
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
voidzero-dev/vite-plus 的其他 Issue
-
triage: not actionable
难度 2/5 1-3 小时 新手友好度 85/100
voidzero-dev/vite-plus#3296 · 1 条评论 ·
维护者通常 1 天内回复
-
pending triage
难度 2/5 1-3 小时 新手友好度 63/100
voidzero-dev/vite-plus#3235 ·
维护者通常 1 天内回复
-
Docker guide: the runtime stage needs libatomic1 for Node.js 25 and later可能已有人在做 @kshanxs 于 11 天前认领。 未关闭documentation
难度 2/5 1-3 小时 新手友好度 84/100
voidzero-dev/vite-plus#3219 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
pending triage
难度 2/5 1-3 小时 新手友好度 72/100
voidzero-dev/vite-plus#2882 · 2 条评论 ·
维护者通常 1 天内回复
-
Upgrade tsdown and its extensions to 0.23.5可能已有人在做 @fengmk2 于 1 天前认领。 未关闭
voidzero-dev/vite-plus#3342 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 voidzero-dev/vite-plus 的全部 Issue
相似的 Issue
-
Windows docs: pin a tested ConPTY version for Kitty graphics; 1.25.260930003 corrupts large uploads未关闭
难度 1/5 1-3 小时 新手友好度 88/100
raphamorim/rio#2021 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
hydro-project/infinity#187 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
near/near-sdk-rs#1676 ·
维护者通常 2 天内回复
-
auto:producer auto:security
难度 2/5 1-3 小时 新手友好度 66/100
fritzprix/libr-agent#2595 ·
维护者通常 1 天内回复
-
area:fs type:fix
难度 2/5 1-3 小时 新手友好度 76/100
Tripstack-Corp/spyc#1002 ·
维护者通常 1 天内回复