Repository navigation
fix(release): publish Windows file-lock retries in v6.2.1 - #212
Merged
Merged
Conversation
Release highlights: - keep indexing reliable on Windows machines where antivirus, search indexing, or sync clients such as OneDrive briefly hold new files Release details: - **Windows reliability:** manifest, state, cache, config, model, and lock-owner writes retry the transient EPERM, EACCES, and EBUSY renames that Windows reports while another process holds a file, for about two seconds, and directory removals retry busy or not-yet-empty directories; other platforms and other errors behave as before - **Tests:** integration test timeouts scale by the factor measured on Windows runners, where spawning git, fsync, and small-file churn cost 9 to 16 times more than on Linux - **Documentation:** the troubleshooting guide explains what to do if Windows still reports EPERM, EBUSY, or ENOTEMPTY Verification: - pass pnpm validate with 540 Core tests and 24 landing tests plus coverage, API, CLI and MCP smoke, builds, packaging, license policy and release smoke checks - pass Quality gate, Linux x64, macOS ARM64 and Windows x64 portability, Commitlint and CodeQL analysis on the fix pull request - measure Windows and Linux runners side by side: a demo ingest takes 409 ms against 147 ms and a warm search 23.5 ms against 14.8 ms, in line with the operating system's process and file costs
|
🎉 This PR is included in version 6.2.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release highlights:
such as OneDrive briefly hold new files
Release details:
transient EPERM, EACCES, and EBUSY renames that Windows reports while another process holds a
file, for about two seconds, and directory removals retry busy or not-yet-empty directories;
other platforms and other errors behave as before
spawning git, fsync, and small-file churn cost 9 to 16 times more than on Linux
EPERM, EBUSY, or ENOTEMPTY
Verification:
and MCP smoke, builds, packaging, license policy and release smoke checks
analysis on the fix pull request
a warm search 23.5 ms against 14.8 ms, in line with the operating system's process and file
costs