Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

prune_kv_values_updated_before emits actions in HashMap order; replay fails with `kv clear mismatch`

Aperta
  • Qualcosa non va?
#57 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

@akhil9tiet ci sta già lavorando.

Dal 4/10/2026.

  • #62 di @akhil9tiet — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
node.js, rust
Ambito
distributed-systems

Direzione di ricerca

Start in src/lib.rs at prune_kv_values_updated_before (around lines 3411-3427), then inspect get_kv_all_keys around lines 3360-3362 and the kv_metadata declaration around line 1715. Reproduce the Node.js SDK scenario with multiple matching keys and verify that replay emits and consumes KV actions in a consistent order.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Summary

An orchestration that prunes two or more KV keys in one turn fails on a later replay with nondeterministic: kv clear mismatch. The orchestration code is deterministic. The order of the actions that the runtime emits is not.

Where

A HashMap has a random seed per map. So the iteration order differs between two replays of the same turn, also inside one process.

How it fails

  1. Execution 1 writes the keys a to f and continues as new.
  2. Execution 2 calls prune_kv_values_updated_before(cutoff). All six keys match. The turn records six KeyValueCleared events in some order.
  3. A later turn replays the same code. The six ClearKeyValue actions come out in a different order.
  4. The replay engine compares the first action with the first event, finds another key, and fails the orchestration.

Reproduction

Reproduced with duroxide 0.1.30 on SQLite, through the Node.js SDK:

runtime.registerOrchestration('Prune', function* (ctx, input) {
  if (!input || !input.second) {
    for (const k of ['a', 'b', 'c', 'd', 'e', 'f']) ctx.setValue(k, 'x');
    yield ctx.continueAsNew({ second: true });
    return '';
  }
  const now = yield ctx.utcNow();
  const pruned = ctx.pruneKvValuesUpdatedBefore(now + 60_000); // clears all six keys
  yield ctx.utcNow();
  yield ctx.utcNow();
  return `pruned ${pruned}`;
});

6 of 6 instances failed, for example with:

nondeterministic: kv clear mismatch: action=ClearKeyValue { key: "d" } vs event=KeyValueCleared { key: "a" }

Impact

  • An orchestration that calls prune_kv_values_updated_before with more than one matching key can fail for good. With n keys, two replays agree on the order with a chance of 1 in n!.
  • get_kv_all_keys and get_kv_all_values hand the same random order to orchestration code. Code that loops over the result and schedules work per key is nondeterministic for the same reason.

Suggested fix

  • Sort the keys in prune_kv_values_updated_before before the actions are emitted.
  • Return sorted keys from get_kv_all_keys, or keep the KV state in a BTreeMap.

Tracked in #55.

Lingua principale
Rust
Stelle
221
Fork
61
Merge medio
3g 5h
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/duroxide

Tutte le issue di microsoft/duroxide

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.