Workspace inbound sync monitor can crash with NoRealm

[vxgmichel]

In some cases, the following crash can occur on the workspace_inbound_sync monitor:

libparsec_client::monitors::workspace_inbound_sync] Workspace 6e743ef9-3662-4218-b0db-6aa62c24f47a: stopping due to unexpected error: NoRealm

This happen due to the fact the realm has not been created on the server yet, meaning the workspaces_bootstrap monitor has not processed it yet.

This typically does not happen because the workspace_inbound_sync monitor only reacts to RemoteChange and MissedServerEvents. That means that when a workspace is created, the workspaces_bootstrap monitor has plenty of time to bootstrap it until the first RemoteChange event occurs.

However, if the workspace is created while being offline, then there's a good chance that the MissedServerEvents wakes up the monitor while the workspace is not bootstrapped.

[vxgmichel]

Other warning have been recorded for the workspace_outbound_sync monitor, which might be the sign of a similar issue:

[2025-02-15T15:48:33Z ERROR libparsec_client::monitors::workspace_outbound_sync] Workspace 95e17852-d9a7-420c-b8ea-4aebf331416c: stopping due to unexpected error: Unexpected server response: return ok status but with invalid items
[2025-02-15T15:48:38Z ERROR libparsec_client::monitors::workspace_outbound_sync] Workspace f0000000-0000-0000-0000-000000000004: stopping due to unexpected error: Unexpected server response: return ok status but with invalid items
[2025-02-15T15:48:38Z WARN  libparsec_client::monitors::workspace_outbound_sync] Workspace f0000000-0000-0000-0000-000000000004: stopping due to sub-task unexpectedly stopped