Closed Zhehan-Z closed 1 month ago
@Zhehan-Z lol, the RTC is not ready for testing yet, but thank you for letting us know!
@tiensonqin I noticed this too there was no announcement but seems that account creation was unlocked and works:
Should we try this or not?
Current quick workaround: after the change gets reverted, immediately change status to No Status. Then the correct status shows up and gets synced. No idea why that might work.
@Zhehan-Z lol, the RTC is not ready for testing yet, but thank you for letting us know!
So the whole ‘sync’ function is not yet ready for testing? Or it’s just the RTC toggle?
this bug has been fixed. we'll open testing rtc later(no specific date yet), so closing this issue for now.
So the whole ‘sync’ function is not yet ready for testing? Or it’s just the RTC toggle?
sync for db-version is not ready for testing now.
Search first
What Happened?
When the user tries to change a task's status to 'DONE' or any other option, the edit is automatically reverted the moment sync begins working. This makes directly editing task status in a synced DB impossible, and unfortunately breaks the whole workflow.
Reproduce the Bug
Expected Behavior
The status change should be correctly registered and accepted by the sync server.
Screenshots
Browser, Desktop or Mobile Platform Information
OS: macOS Sonoma 14.4 (23E214) Browser: Safari 17.4 (19618.1.15.11.12) Logseq DB: 0.10.10
Additional Context
Every time the sync operation that reverts the edit happens, a new line appears in the console log:
[Log] rtc/apply-remote-ops-log (db-worker.js, line 880)
No other lines appear, and no further information after expanding that entry.
Are you willing to submit a PR? If you know how to fix the bug.