Repository navigation
fix(loro.js): reject invalid MovableList move/set refs (port Rust #1125) - #1168
Merged
Merged
Conversation
Drive the Rust WASM build and loro.js with the same random multi-peer edits, crossing engines on every sync, and require equal values, versions, per-element metadata and events. Profiles that diverge on the current MovableList model are recorded as known divergences. Design and findings: context/loro-js-movable-list.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Event deltas that differ only in shape are checked by effect; reverts whose op order Rust leaves to hash order are checked by value and replicated from Rust; peers that both engines reject are retired; peer IDs are never reused; undo stays unchained; the minimizer keeps those rules. See context/loro-js-movable-list.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…list-differential # Conflicts: # AGENTS.md
…undo unchained Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…se diff shape differs Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…allow root Both follow Rust issues listed in context/loro-js-movable-list.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ust reference Load Rust through tests/support/rust-reference.ts like the other differential suites, so it runs in `pnpm test` (and in CI's test-loro-js) and skips without a WASM build. Drop the separate workflow and scripts. insert/delete now converges on main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MovableList keeps a Fugue sequence of list items and elements whose position and value are last-writer-wins registers, as Rust does. Moves of concurrently deleted elements, deletes after moves, snapshots (list item, element and last-set IDs, dead items), metadata getters, version transitions, revertTo/applyDiff (Rust's apply_delta), undo and events now match Rust. Snapshot-hydrated documents replay history before concurrent imports, and a few shallow-snapshot incompatibilities are fixed. The differential suite passes every profile. Design and remaining gaps: context/loro-js-movable-list.md. Rebuilt on current main: MovableList joins #1126's per-container snapshot completion (its snapshot state names Rust IDs), applyDiff/revertTo/undo use main's port of Rust #1138's apply_delta on the new model, and undo transforms only over changes the UndoManager did not make. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s-movable-list-model
…ules Decoding deferred snapshot history dropped pending changes. Shallow imports now check the unknown part of each change like is_before_shallow_root, and an import that only adds pending changes creates their root containers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
main's diff() reports such a child by its ops, including map keys set and deleted again, as Rust does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…acker A causal view per concurrent op made importing concurrent moves O(n^2). Like Rust's Tracker::checkout, keep a tracker version and a per-position delta metric that moves incrementally between op versions; see context/loro-js-movable-list.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A failed import no longer leaves history, pending changes, version,
containers, state or events half applied. In-place history changes are
journaled and undone, state is rebuilt only when it had changed, events are
emitted after success.
Details: context/import-batch-atomicity.md ("loro.js").
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…heir history Port of #1125; see context/loro-js-movable-list.md (Validation). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lues A MovableList replaced by a plain value made the comparison enumerate the container and hit its guarded element sequence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Rust-model MovableList passes seeds 0-599 of the #1141 fuzz with all oracles in lockstep with Rust; main failed 144 of seeds 0-299. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…y_delta Without moved children the delta was walked in order, which gave the ops other IDs than Rust's and later deletes by ID missed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…diff() A child created in the range whose keys were all set and deleted again is listed by Rust and omitted by loro.js, also on main and for any parent; see context/loro-js-movable-list.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s-movable-list-model # Conflicts: # context/loro-js-movable-list.md
This was referenced Sep 29, 2026
Contributor
WASM Size Report
|
The performance context still described main's MovableList snapshot special case and #1163 as open. Measurements are in context/loro-js-performance.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
canTransition walked the position tree once per insert op, which made checkout, diff and revertTo O(insert ops * positions). Collect the runs and check them in one containsIdRuns call, as the List branch does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The changeset named a test:differential script that does not exist. Rust's diff() can list a sequence with an empty delta where loro.js omits it (context/loro-js-movable-list.md). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s-movable-list-model # Conflicts: # context/loro-js-movable-list.md
…r import Each import copied the whole snapshot-sequence table for rollback, so its cost grew with the number of snapshot-hydrated containers. Record each write in the import journal instead (context/import-batch-atomicity.md). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Last PR of the MovableList stack, based on #1167 (review only the commits after it). It ports the merged Rust #1125 to loro.js: a MovableList move or set that cannot mean anything is rejected, and the whole import or batch rolls back. A move or set of a deleted element stays valid and keeps its concurrent CRDT meaning.
#validateMovableListRefsindocument.tsmirrorsOpLog::validate_movable_list_elem_refs_since. It runs on every imported change after integration: FastUpdates, non-initializing snapshots andimportBatch. Like Rust, it skips the snapshot that seeds an empty document. It rejects aMove/Setwhose element:movable-list-insertinto the same list;shallow_root_has_movable_list_elem), that is, it was deleted before the root.MovableListState.applyMovealready rejects afrom/tooutside the op-index range of the op's causal view before it mutates anything. With #1167, that rejection also rolls the import back.Complexity:
(peer, lamport)to an op ID by binary search over the peer's indexed changes: O(log changes).Validation
pnpm -C loro-js check: passes.loro-js/tests/movable-list-invalid-ops.test.tsportscrates/loro/tests/movable_list_invalid_ops.rs(12 tests):importBatchrollback;main(with fix: reject malformed movable list move/set ops on import instead of aborting #1125) through a module alias. 11 of the 12 tests pass unchanged apart from the error pattern; the twelfth needs loro.js's codec. The two agree on values, which imports are rejected, the rollback, and the document staying usable. Error texts differ: Rust says "Decode error" / "movable list diff retains N items but state only has M", loro.js says "causal history" / "out of range".588aa35d(later commits only change docs), with a Rust reference built from currentmain:map,list,text,counter,movableList,nested, all oracles, lockstep with Rust: seeds 0–799 pass. With the same settings,mainfails 24 of seeds 0–49 (19 checkout-vs-replay on a MovableList, 5 lockstep).Known limitations
Rust rules that loro.js does not copy; both are edge cases, listed in
context/loro-js-movable-list.md:attachfails.Merge order
import/importBatch(this PR's base).🤖 Generated with Claude Code