Repository navigation
docs: explain pending import persistence and import status - #54
Merged
Merged
Conversation
Model: gpt-6.1-sol
This was referenced Oct 22, 2026
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loro-docs | d5adcca | Commit Preview URL Branch Preview URL |
Oct 22 2026, 01:03 PM |
Document WASM 1.17.0, pure TypeScript 0.4.0 and Rust 1.17.0 availability; update persistence anchors and keep language binding releases separate. Model: gpt-6.1-sol
zxch3n
marked this pull request as ready for review
October 22, 2026 12:58
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.
Snapshots omit imported operations that are still waiting for causal dependencies. The previous persistence advice could therefore discard received update bytes before a checkpoint could safely restore them after a restart.
Document
exportPendingUpdates(), available sinceloro-crdt@1.17.0andloro.js@0.4.0. Cover its read-only behavior,Uint8Array | undefinedresult, ordinaryimport()recovery, and the published Rust 1.17.0 method. Link the FFI binding source separately; availability in a released language package must be checked independently.Explain consistent snapshot-plus-pending checkpoints, clearing a stale pending record on
undefined, keeping the previous checkpoint on export failure, and preserving recovery material before advancing durable cursors or deleting original updates. Correct import-status examples to useMap<PeerID, CounterSpan>and requiredpending: Map<PeerID, CounterSpan> | null. An individual import result is not a query of the whole pending queue, and an empty queue does not establish synchronization. Update the six API/concept/tutorial pages and all links to the released persistence heading.Validation at
d5adccad15c7daa20b5e87f4def908fda3cf67ac:loro.js): four successful executions. The persistence example has ten throwing assertions covering pending B, snapshot exclusion, repeated export, restart, dependency A, and clearing the old pending record.skipLibCheck.pnpm buildpassed: 81 generated Next.js pages, 72/72 rendered SEO checks, and the OpenNext bundle.pnpm test:seopassed 5/5.pnpm testpassed 161/161 existing code-block executions. That runner pinsloro-crdt@1.13.3and skipsno_run; these results are separate from the released-package checks above.git diff --checkpassed.Original rendered persistence screenshot (captured before the release labels and heading were updated):
Related: Loro core #1220, Rust release #1221, FFI #17, Lody investigation #1815. This documentation PR has not been deployed.