logseq / logseq/db-test

Sync issue: "pending server changes" does not reflect reality

Open
#947 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Search first
  • I searched and no similar issues were found
What Happened?

I did some changes in the desktop app and using the CLI and it synced with the server sucessfully, but in browser it says "0 pending server changes". It does not even recognizes that it is out of sync, so the status can not be trusted.

Reproduce the Bug
  1. Open Logseq in browser: https://test.logseq.com/#/all-pages
  2. Check if latest changes are synced
  3. Check if sync status match
Expected Behavior

The sync status should reflect reality and should be trustworthy in that.

Screenshots
Image

Here you see new pages from testing the CLI examples in the GUI.

Files

No response

Browser, Desktop or Mobile Platform Information

NixOS 25.11.10684.8fd9daa3db09
Google Chrome 147.0.7727.101
Logseq Web 2.0.1 (6db2382)
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260617

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.
  • I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the mismatch at https://test.logseq.com/#/all-pages with the listed browser, web, and desktop versions, then trace how the browser displays sync status after changes made through the desktop app and CLI. Done means the status reflects whether the browser has pending server changes and remains trustworthy across these clients.

Written by the indexing model from the issue text.

Assessment

Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.