Skip to content

Status bar shows "Receipt: local state not yet received by server" despite active sync #68

Description

@dariy-vel

YAOS plugin version

2.1.0

Server deployment commit SHA

7137154 / 0.3.0

Relevant logs or error text

{"seq":260,"source":"receipt","msg":"receipt-server-echo","details":{"serverSvBytes":22,"candidateBytes":22,"hasCandidate":true,"serverDominatesCandidate":false,"serverAppliedLocalState":false}}
{"seq":293,"source":"receipt","msg":"receipt-server-echo","details":{"serverSvBytes":22,"candidateBytes":22,"hasCandidate":true,"serverDominatesCandidate":true,"serverAppliedLocalState":true}}
{"seq":295,"source":"receipt","msg":"receipt-server-echo","details":{"serverSvBytes":22,"candidateBytes":22,"hasCandidate":true,"serverDominatesCandidate":false,"serverAppliedLocalState":false}}
Image

What you did

  1. Connected the YAOS plugin to a self-hosted Cloudflare Worker instance.
  2. Observed status bar displaying "Receipt: local state not yet received by server".
  3. Created and deleted a temporary note (00-jots/2026-08-22.md), which incremented serverSvBytes and temporarily set serverAppliedLocalState: true (seq: 293).
  4. Made a local edit, which recaptured a candidate with matching byte length (candidateBytes === serverSvBytes).
  5. Observed serverDominatesCandidate evaluate to false and serverAppliedLocalState flip back to false (seq: 295), triggering the false-positive warning despite live synchronization.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions