Move does not work after fully replicated

[raineorshine]

Platform: Chrome
Seed: 1m
Fully replicated

Steps to Reproduce

Drag a thought into another thought.

Current Behavior

The thought does not move.

There's no error or message in the console. Refreshing the app and waiting for the initial render also confirms that no move occurs.

Screen.Recording.2025-05-01.at.11.43.42.AM.mov

Expected Behavior

Thought should move to the new parent.

[obezzad]

One reason for this is the lack of proper concurrency support at browser level, although they're working on it (goals and use cases included there), making the write bottlenecked by all pending reads competing on the same lock. Refreshing the page kills the worker while OPFS handle is still open leading to a stale lock for a while as discussed in #3. PowerSync seems to recover from the deadlock at the cost of data loss. A way to mitigate this at application level, which is already implemented, is to minimize slow read queries so that it's less likely to refresh the page before the changes are committed. In the current version, after full sync, the tree must show faster and move ops to happen as expected.

The root issue seems to be mainly at PowerSync level and requires custom development effort from our end; there are known workarounds that they didn't implement yet as they seem quite challenging internally and they claim they come with other performance trade-offs.