Repository navigation
docs: record desktop traffic and pending persistence findings - #1815
Merged
Merged
Conversation
Model: gpt-6.1-sol
This was referenced Oct 22, 2026
Update the bilingual investigation proposal to the rebased Loro core baseline and preserve checkpoint error-reporting requirements. Model: gpt-6.1-sol
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.
Related issue
No linked issue. Same-repository investigation and review handoff.
Problem / pressure
A reported idle-night traffic spike requires separating network-error symptoms from mechanisms that repeatedly transfer full snapshots. Source inspection and bounded synthetic experiments found a reproducible incomplete-import recovery loop and a separate pending-update persistence gap; neither establishes the reporter's actual traffic source.
Summary
Related implementation PRs: Loro core #1220, FFI #17, website #54.
Visual explanation
The diagram explains the persistence boundary. A durable receive checkpoint is distinct from applied completeness and synchronization.
Before / after
Test plan
pnpm run docs status: completed.pnpm run docs check: still reports 84 existing errors and 71 warnings; none references the new note, and no SHA-protected topic changes were reported.git diff --cached --check: passed before commit.pnpm checkandpnpm format: attempted; this checkout has no installed workspace dependencies, so they stop on missingtsgo/oxfmt. No application-wide green-check claim is made.Context handoff
This internal contribution prepares the complete investigation and the related core/binding/documentation changes for independent review on another computer. Review the linked PR heads rather than relying on previous completion summaries. Core #1220 has been rebased onto main
136b944f, retains the released Rust 1.16.2 fixes, and is verified ated71753b7a689eb77097b54102b8e20b92444ef6. FFI review pins must retain that released baseline; publishing still requires a released core containing the API. No authoring transcript or private user payload is included.