EloAdaptor: waitForReachingServerVersion() never resolves on a one-shot backfill (compare runs before the un-awaited imports land)
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Accessibilité débutants
- 76/100
- Type d'issue
- Bug
- Clarté
- Clairement spécifiée
- Activité
- Active
- Stack technique
- typescript
- Domaine
- distributed-systems
Piste de recherche
Start in packages/loro-adaptors/src/elo-adaptor.ts, focusing on applyUpdate(), importEloContainer(), and waitForReachingServerVersion(). Run the minimal reproduction with the listed loro-adaptors, loro-crdt, loro-protocol, and Bun or Node versions, then verify that a one-shot backfill resolves the wait without a redundant update. Add a regression test covering the EloAdaptor path and the existing LoroAdaptor control case.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Summary
EloAdaptor.waitForReachingServerVersion() never resolves when the whole backfill arrives in a single applyUpdate call (the normal join path), even though the document does receive the data. The same scenario with LoroAdaptor (%LOR) resolves immediately.
Cause
EloAdaptor.applyUpdate fires importEloContainer(...) for each container without awaiting it (decryption is async), then compares this.doc.version() with initServerVersion in the same synchronous tick. The comparison therefore runs against the version before the imports land, and nothing re-runs it once they do:
// packages/loro-adaptors/src/elo-adaptor.ts (main, unchanged since 6570a2ee)
applyUpdate(updates: Uint8Array[]): void {
if (this.destroyed || !updates?.length) return;
for (const containerBytes of updates) {
try {
this.importEloContainer(containerBytes).catch(err => { ... }); // async, not awaited
} catch (error) { ... }
}
if (this.initServerVersion && !this.hasReachedServerVersion) {
const cmp = this.doc.version().compare(this.initServerVersion); // pre-import version
if (cmp != null && cmp >= 0) this.reachServerVersionPromise.resolve();
}
}
The promise resolves only when the server version is empty (handleJoinOk), or if some later unrelated update happens to arrive on the room and re-runs the compare.
Minimal reproduction
[email protected], [email protected], [email protected], Bun 1.x (Node behaves the same). No other code.
// Minimal repro: EloAdaptor.waitForReachingServerVersion() never resolves on a
// one-shot backfill. No application code: [email protected] + loro-crdt only.
import { LoroDoc } from "loro-crdt";
import { EloAdaptor, LoroAdaptor } from "loro-adaptors/loro";
const key = new Uint8Array(32).fill(7);
const config = { getPrivateKey: async () => ({ keyId: "k1", key }) };
const sleep = (ms: number) => new Promise<void>((r) => setTimeout(r, ms));
const ctx = (sink: Uint8Array[][]) =>
({
send: (u: Uint8Array[]) => void sink.push(u),
onImportError: (e: Error) => { throw e; },
onJoinFailed: (reason: string) => { throw new Error(reason); },
}) as any;
const race = (p: Promise<void>, ms: number) =>
Promise.race([p.then(() => "resolved"), sleep(ms).then(() => `still pending after ${ms} ms`)]);
async function scenario(label: string, make: (doc: LoroDoc) => EloAdaptor | LoroAdaptor) {
// 1. A peer with content joins an empty room: its adaptor sends the snapshot.
const docA = new LoroDoc();
docA.setPeerId(1n);
docA.getMap("m").set("hello", "world");
docA.commit();
const sentByA: Uint8Array[][] = [];
const a = make(docA);
a.setCtx(ctx(sentByA));
await a.handleJoinOk({ version: new Uint8Array(0) } as any);
const backfill = sentByA.flat();
const serverVersion = docA.version().encode();
// 2. A fresh peer joins the room whose server version is A's version, then
// receives the whole backfill in ONE applyUpdate call (what a join does).
const docB = new LoroDoc();
docB.setPeerId(2n);
const b = make(docB);
b.setCtx(ctx([]));
await b.handleJoinOk({ version: serverVersion } as any);
const waiting = b.waitForReachingServerVersion();
b.applyUpdate(backfill);
const outcome = await race(waiting, 2000);
const cmp = docB.version().compare(docA.version());
console.log(`[${label}] backfill containers: ${backfill.length}`);
console.log(`[${label}] waitForReachingServerVersion(): ${outcome}`);
console.log(`[${label}] docB has the data: ${docB.getMap("m").get("hello") === "world"}; docB.version() vs server: ${cmp} (0 = equal)`);
if (outcome !== "resolved") {
// Proof that only the timing of the compare is wrong: a second, redundant
// applyUpdate re-runs the compare after the first import landed.
b.applyUpdate(backfill);
console.log(`[${label}] after a second (redundant) applyUpdate: ${await race(waiting, 500)}`);
}
console.log("");
}
await scenario("EloAdaptor (%ELO)", (doc) => new EloAdaptor(doc, config));
await scenario("LoroAdaptor (%LOR, control)", (doc) => new LoroAdaptor(doc));
Output:
[EloAdaptor (%ELO)] backfill containers: 1
[EloAdaptor (%ELO)] waitForReachingServerVersion(): still pending after 2000 ms
[EloAdaptor (%ELO)] docB has the data: true; docB.version() vs server: 0 (0 = equal)
[EloAdaptor (%ELO)] after a second (redundant) applyUpdate: resolved
[LoroAdaptor (%LOR, control)] backfill containers: 1
[LoroAdaptor (%LOR, control)] waitForReachingServerVersion(): resolved
[LoroAdaptor (%LOR, control)] docB has the data: true; docB.version() vs server: 0 (0 = equal)
The third line shows the document is complete while the promise is still pending; the fourth shows that merely re-running the comparison after the import resolves it, so the only defect is the timing of the compare.
Suggested fix
Run the comparison after the imports have settled, e.g.
applyUpdate(updates: Uint8Array[]): void {
if (this.destroyed || !updates?.length) return;
const imports = updates.map(bytes =>
this.importEloContainer(bytes).catch(err => this.ctx?.onImportError(toError(err), [bytes]))
);
void Promise.allSettled(imports).then(() => {
if (this.destroyed) return;
if (this.initServerVersion && !this.hasReachedServerVersion) {
const cmp = this.doc.version().compare(this.initServerVersion);
if (cmp != null && cmp >= 0) this.reachServerVersionPromise.resolve();
}
});
}
(Alternatively, subscribe to the doc's import events and compare there, which also covers imports triggered outside applyUpdate.)
Impact
Any client that gates "initial sync done" on waitForReachingServerVersion() for an %ELO room waits forever on a one-shot join backfill and has to hand-roll a content-side wait instead. Happy to open a PR with the fix above and a test if you want one.
- Langage dominant
- TypeScript
- Étoiles
- 40
- Forks
- 12
- Merge moyen
- 4 j 1 h
- PR mergées (30 j)
- 1
Préparer son environnement
Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de loro-dev/protocol
-
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 25/100
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 25/100
-
bug
Difficulté 3/5 1-2 jours Accessibilité débutants 48/100
-
bug
Difficulté 3/5 1-2 jours Accessibilité débutants 68/100
Toutes les issues de loro-dev/protocol
Issues similaires
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 80/100
aws/agentcore-cli#2606 ·
Les mainteneurs répondent en général sous 1 jour
-
ai-driven-qa bug Cosmetic
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
Les mainteneurs répondent en général sous 1 jour
-
ai-driven-qa bug claude Minor
Difficulté 2/5 1-3 heures Accessibilité débutants 64/100
linagora/twake-mail-admin#301 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
Les mainteneurs répondent en général sous 1 jour
-
reproduced
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
anomalyco/opencode#56038 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour