Repository navigation
fix: a full workspace registry no longer drops every client workspace - #13
Merged
Merged
Conversation
When the registry reached 64 entries, WorkspaceAdd made room by dropping each workspace whose path did not exist on the server's filesystem. A detached or mirror workspace's path is the client's, so it never exists there, and every one of them was dropped at once. On 2026-10-30 one add on the production server took the registry from about 20 workspaces to 3, and every git tool in those trees failed until they were registered again. Only a server-local (shared) workspace is now judged by a local stat. A registry full of client workspaces refuses the add instead of dropping one.
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.
No description provided.