Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Concurrent first runs of `vp config` in linked worktrees fail with "could not lock config file"

未关闭
  • 哪里不对？
#2,959 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@naokihaba 已经在做这个了。

开始于 2026年10月9日。

评估

这个 Issue 还没有评估数据。

描述

pending triage
Describe the bug

This is a follow-up to #2849.

While prevents vp config from rewriting git config values that are already up to date, the very first run in a fresh clone still has to write them because core.hooksPath, vp.hooks.dir, and vp.hooks.prefix are not set yet.

Linked worktrees share the same .git/config file. Because git fails immediately instead of waiting when config.lock exists, running the initial vp config concurrently across multiple worktrees causes write collisions:

error: could not lock config file /path/to/repo/.git/config: File exists

The command then exits with code 1. If this runs inside a prepare script, the package manager treats it as a lifecycle script failure and aborts the install.

We run into this when setting up multiple worktrees in parallel right after cloning, before any single worktree finishes its setup. Once one command succeeds, subsequent runs simply skip writing and never fail.

Reproduction

https://github.com/naokihaba/vite-plus-config-first-run-lock-repro

Steps to reproduce
1. Clone the reproduction repository and install the dependencies.

   
   git clone https://github.com/naokihaba/vite-plus-config-first-run-lock-repro
   cd vite-plus-config-first-run-lock-repro
   pnpm install --ignore-scripts
   

2. Run the reproduction with two worktrees.

   
   pnpm repro
   

3. You can also run it with four worktrees or use the global CLI if needed.

   
   REPRO_WORKTREES=4 REPRO_ROUNDS=15 bash reproduce.sh
   bash reproduce.sh --global
   

In each round, the script creates a fresh repository with linked worktrees and runs `vp config --no-agent` across all of them at once, so every command acts as a first run.

If at least one lock failure occurs, the script prints a summary and exits with code 0.
System Info
$ vp env current
Node.js:
  Version    24.21.0
  Source     lts
  Bin Path   /Users/naokihaba/.vite-plus/js_runtime/node/24.21.0/bin/node
  Installed  true
  Mode       managed

Package Manager:
  Name       pnpm
  Version    12.10.1
  Source     lockfile or config
  Bin Paths  
    pnpm     /Users/naokihaba/.vite-plus/package_manager/pnpm/12.10.1/pnpm/bin/pnpm
    pnpx     /Users/naokihaba/.vite-plus/package_manager/pnpm/12.10.1/pnpm/bin/pnpx
  Installed  false
  Mode       managed

$ vp --version
vp v1.0.0

Local vite-plus:
  vite-plus  v1.0.0

Tools:
  vite             v8.3.1
  rolldown         v1.2.11
  vitest           v5.0.1
  oxfmt            v0.70.0
  oxlint           v1.85.0
  oxlint-tsgolint  v7.0.2003
  tsdown           v0.23.0

Environment:
  Package manager  pnpm default
  Node.js          v24.21.0

# Additional
git version 2.55.0
macOS 27.0 (arm64)
Node.js v24.20.0 from PATH for the local-mode runs
Used Package Manager

pnpm

Logs
Validations
主要语言
Rust
星标
6k
派生
274
平均合并
1 天 11 小时
30 天内合并 PR
206

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

voidzero-dev/vite-plus 的其他 Issue

查看 voidzero-dev/vite-plus 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。