Comment/Comments tag's "Created At" and "Updated At" reset to 0 after enable sync
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?
After enabling sync and re-downloading from the sync server, the "Created At" and "Updated At" timestamps of the Comment/Comments tag are reset to 0. See the reproduction steps below.
Reproduce the Bug
- Go to "All graphs" and create a new graph.
- Enable Logseq Sync. cmd+k search "tag", go to the
#Tagpage, noticed theCommentandCommentstag all has the correct creation and last modified time. - In "All graphs" page, select "Delete local graph" from the three dot menu, then re-download it from the sync server.
- Go to the
#Tagpage again, the creation and last modified time forCommentandCommentstag all reset to 0.
Expected Behavior
The creation and last modified time should remain unchanged.
Screenshots
Files
No response
Browser, Desktop or Mobile Platform Information
Windows 11, 2.0.1-alpha+nightly.20260728, commit 9a11243.
Also can reproduce on test.logseq.com.
Uses self-hosted sync server.
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through All graphs, Logseq Sync, and the #Tag page, including a re-download from the self-hosted sync server. Trace how Comment and Comments tag timestamps are handled during sync and verify that Created At and Updated At remain unchanged after deleting and re-downloading the local graph.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100