%ELO adaptor mislabels deltas as snapshots and strips version vectors
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- rust
- Domain
- distributed-systems
Research direction
Start in rust/loro-websocket-client/src/lib.rs:1114-1155 and read protocol-e2ee.md for the DeltaSpan requirements. Trace local update export and initial join handling, then verify that deltas carry peerId/start/end and the document version vector, while genuine snapshots remain limited to ExportMode::Snapshot and per-peer counters advance correctly.
Written by the indexing model from the issue text.
Description
rust/loro-websocket-client/src/lib.rs:1114-1155
- Each local update is wrapped as an “Snapshot” record with vvCount = 0, even though the payload is just a
delta blob. That violates protocol-e2ee.md (DeltaSpan must carry peerId/start/end) and prevents receivers
or the server from deduplicating or backfilling. - Initial join also sends a full snapshot regardless of negotiated version, re-emitting an empty VV that
hides actual counters. - Fix: When exporting CRDT deltas, build a DeltaSpan header with peerId/start/end, include the doc’s version
vector, and only emit genuine snapshots when exporting ExportMode::Snapshot. Ensure the adaptor stores and
increments counters per peer so version negotiation works cross-language.
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
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.
More from loro-dev/protocol
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in loro-dev/protocol
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·