fix(storage): add retry logic for UV_UNKNOWN errors on Windows #6913
+34
−12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On Windows, storage operations can fail with UV_UNKNOWN errors due to transient file locking from anti-virus software or other processes. This change: - Adds retry logic (3 attempts with exponential backoff) for transient errors including UV_UNKNOWN, EBUSY, EPERM, EACCES, and EAGAIN - Adds detailed error logging with path, pathLength, errno, and syscall to help diagnose storage operation failures
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No Duplicates FoundThe searches across multiple relevant keywords only returned the same PR (likely the one being created). No duplicate or related open PRs were found that address:
Conclusion: This appears to be a unique fix. You're safe to proceed with this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
On Windows, storage operations can fail with
UV_UNKNOWNerrors due to transient file locking from anti-virus software (e.g., FortiClient) or other processes accessing the files.Solution
Added retry logic (up to 3 retries with incremental delays) before giving up, which allows time for anti-virus or other processes to release the file lock.
Change
UV_UNKNOWN,EBUSY,EPERM,EACCES, andEAGAINerrors