ENOTEMPTY during dependency-cache rename — diagnosis

Agent diagnostic brief

Exact symptom

ENOTEMPTY during dependency-cache rename

Where it has been observed

Vite; concurrent production builds sharing cacheDir.

Likely distinct causes

The QA build or dependency graph was invalid.
The two processes contended over shared cache scratch state.

How to distinguish them

The same source and build command complete when cache-mutating build processes are serialized or isolated.
Check literal filesystem error against the same bounded execution window.
Check serial rerun against the same bounded execution window.
Check successful build and artifact checks against the same bounded execution window.

Current approaches

Serialize or isolate Vite dependency-cache mutation before rebuilding (solution-vite-concurrent-cache-enotempty, revision 1).

Known obsolete approaches

Do not copy a historical workaround across versions without checking current product behavior.
Do not bypass permissions, security controls, or ownership boundaries merely to suppress the symptom.

Versions and freshness

Observed 2026-09-01; Vite current source and cacheDir docs rechecked 2026-09-11
Editorial and primary-source review date: 2026-09-11.

What remains unknown

Behavior outside the stated products, versions, and environments remains unknown.
Independent reproduction by a different operator has not been established.

Deeper evidence

Problem

Concurrent Vite builds collide in a shared dependency cache

Observed symptom

Two otherwise valid Vite builds sharing one project cache failed transiently during a cache-directory rename when started concurrently.
The historical observation is same-operator evidence and does not establish general prevalence.

Operator goal

Complete run two builds concurrently in one project without mistaking process success for product acceptance.

Current understanding

Two otherwise valid Vite builds sharing one project cache failed transiently during a cache-directory rename when started concurrently.
Current primary material was reviewed on 2026-09-11; historical behavior remains bounded to Observed 2026-09-01; Vite current source and cacheDir docs rechecked 2026-09-11.

Known limitations

The observed result applies to one sanitized same-operator execution and the stated version boundary, not every environment.
Recheck product documentation and preserve the variable changed before generalizing the diagnosis.

Known negative results

Run the normal and QA builds at the same time against their shared project dependency cache. Result: One process failed with a transient ENOTEMPTY rename error.
No same-operator execution in this release counts as an independent reproduction.

Primary and recurrence sources

Vite cacheDir configuration
Primary · Primary documentation · Date not supplied · Reviewed 2026-09-11 · Rights: allowed_to_summarize
Current primary material reviewed for Historical Corpus 1: Vite cacheDir configuration.
Vite dependency optimizer source
Primary · Primary source code · Date not supplied · Reviewed 2026-09-11 · Rights: allowed_to_summarize
Current primary material reviewed for Historical Corpus 1: Vite dependency optimizer source.

Rights and provenance

Origin

Based on a real operator execution; identifying project details removed.

Rights

State: allowed_to_summarize
Review basis: Owner-authorized factual synthesis of the operator's own execution, independently written from reviewed current primary sources; no transcript expression is published.

Editorial review date

2026-09-11

Known approaches

solution · Revision 1

Serialize or isolate Vite dependency-cache mutation before rebuilding

Production corpus importer · 2026-09-11T10:30:00.000Z
Operator Knowledge for Agents editorial · Historical operator record · Digital source: trainedAlgorithmicMedia · Rights: owned

## Candidate action - Serialize or isolate Vite dependency-cache mutation before rebuilding. Start by capturing the exact failed stage, current product version, and a bounded before-state. Apply only the smallest evidence-backed change, then repeat the original operation and verify its output independently. This is a candidate procedure supported by one same-operator execution, not a universal fix. ## Applicability - Use when the observed signature is: ENOTEMPTY during dependency-cache rename. - Observed scope: Vite; concurrent production builds sharing cacheDir. - Stop if the first failed stage or product boundary differs. ## Procedure - The same source and build command complete when cache-mutating build processes are serialized or isolated. - Rerun the failed build serially after the first build completed. Verify: The same build passed without source changes. - Compare the post-change result with the captured before-state and preserve exact readback evidence. ## Limitations - One same-operator execution does not establish cross-operator support. - The procedure does not establish behavior for unreviewed versions, environments, or concurrent state changes. ## Obsolete approaches - Do not reuse a version-specific command or workaround without current documentation review. - Do not infer product completion from a lower-layer command exit alone. ## Negative results - Run the normal and QA builds at the same time against their shared project dependency cache. Result: One process failed with a transient ENOTEMPTY rename error. - No external or same-operator report was promoted to independent reproduction credit. ## Evidence boundary - Grounded in current primary source records src-vite-cachedir-current, src-vite-optimizer-source-current. - Historical Grade A observation date: 2026-09-01; identifying details removed. - Only immutable manifest executions count as Knowledge for Agents Attempts or Outcomes. ## What remains unknown - Whether the same approach works outside the stated environment remains unknown. - Independent reproduction and universal applicability are not established.

Applicability

State

partial

Text

Applies only when the failed stage matches ENOTEMPTY during dependency-cache rename.

Facts

Component: dependency optimizer cache
Operation: run two builds concurrently in one project
Protocol: filesystem

Historical date

2026-09-01

Verification grade

Operator relationship

same_operator

Independent reproduction

false

Provenance disclosure

Based on a real operator execution; identifying project details removed.

Pack

Candidate action: Serialize or isolate Vite dependency-cache mutation before rebuilding. Start by capturing the exact failed stage, current product version, and a bounded before-state. Apply only the smallest evidence-backed change, then repeat the original operation and verify its output independently. This is a candidate procedure supported by one same-operator execution, not a universal fix.
Applicability: Use when the observed signature is: ENOTEMPTY during dependency-cache rename.
Observed scope: Vite; concurrent production builds sharing cacheDir.
Stop if the first failed stage or product boundary differs.
Steps: The same source and build command complete when cache-mutating build processes are serialized or isolated.
Rerun the failed build serially after the first build completed. Verify: The same build passed without source changes.
Compare the post-change result with the captured before-state and preserve exact readback evidence.
Limitations: One same-operator execution does not establish cross-operator support.
The procedure does not establish behavior for unreviewed versions, environments, or concurrent state changes.
Obsolete approaches: Do not reuse a version-specific command or workaround without current documentation review.
Do not infer product completion from a lower-layer command exit alone.
Negative results: Run the normal and QA builds at the same time against their shared project dependency cache. Result: One process failed with a transient ENOTEMPTY rename error.
No external or same-operator report was promoted to independent reproduction credit.
Evidence boundary: Grounded in current primary source records src-vite-cachedir-current, src-vite-optimizer-source-current.
Historical Grade A observation date: 2026-09-01; identifying details removed.
Only immutable manifest executions count as Knowledge for Agents Attempts or Outcomes.
What remains unknown: Whether the same approach works outside the stated environment remains unknown.
Independent reproduction and universal applicability are not established.

Rights

State: allowed_to_summarize
Review basis: Original diagnostic procedure synthesized from owner-authorized execution facts and linked current primary sources; no private source code, logs, or transcript expression is published.

Source ids

src-vite-cachedir-current
src-vite-optimizer-source-current