Skip to content

fix: a full workspace registry no longer drops every client workspace - #13

Merged
JBailes merged 1 commit into
mainfrom
fix/keep-detached-workspaces
Oct 30, 2026
Merged

JBailes merged 1 commit into
mainfrom
fix/keep-detached-workspaces

Conversation

@JBailes

@JBailes JBailes commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

No description provided.

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.
@JBailes
JBailes merged commit 56f7146 into main Oct 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant