MCP Inspector queues concurrent local gate runs on a machine-wide lease after measuring that overlap is red by construction
PR #2344, merged 2026-09-12, makes `npm run local:gate` acquire a machine-wide lease via `proper-lockfile` with a 30-second stale takeover, so a gate started in a second worktree waits instead of running alongside the first. The measurement in the PR overturns the issue's own premise: at two concurrent worktrees load inflation was ~1.3x with zero test timeouts, not the 2.5x figure quoted from a four-worktree run, but one arm still went red because the web smokes bind fixed ports 6296-6299 and the second gate hit `PORT IS IN USE at 127.0.0.1:6298`. Three leased gates started within seconds all finished green; `INSPECTOR_SKIP_GATE_LEASE=1` bypasses, and a lock that cannot be created runs unleased with a warning so the lease can never itself fail a gate.
Source
↳ Follow the thread