Skip to content
Discussion options

You must be logged in to vote

Confirmed. The cascade is one mechanism, not a second bug.

packages/workspace/workspace/src/spec.ts:29 declares sessionIds: z.array(sessionId). The durability boundary parses records through parseRecord (packages/storage/storage-domain/src/index.ts:200-209), which throws DomainError('invalid-record', ...) and has no skip path. So one string-valued record fails the workspace domain's open, every service that waits on that domain stays pending, and the client reports whichever downstream call it hit first — directoryPicker/list in your case.

"All conversations are gone" is not data loss: the sessions are on disk and the workspace table never opened, so no list RPC can answer.

Recovery is to…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@xiaoshuai-007
Comment options

Answer selected by xiaoshuai-007
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants