EloAdaptor: waitForReachingServerVersion() never resolves on a one-shot backfill (compare runs before the un-awaited imports land)
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 76/100
- issue の種類
- バグ
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- typescript
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- TypeScript
- スター
- 40
- フォーク
- 12
- 平均マージ
- 4日 1時間
- マージ済み PR(30日)
- 1
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
loro-dev/protocol のほかの issue
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 25/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 48/100
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 68/100
loro-dev/protocol の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
homarr-labs/homarr#7191 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
AvaProtocol/ava-sdk-js#276 ·
メンテナーはふだん 1 日以内に返信
-
useFragment does not require `variables` when the fragment's variables type has required fieldsオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
apollographql/apollo-client#13493 ·
メンテナーはふだん 1 日以内に返信