Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

已关闭
  • 哪里不对？
#57 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@akhil9tiet 已经在做这个了。

开始于 2026年10月4日。

  • #62 来自 @akhil9tiet —— 未关闭
  • #67 来自 @waldemort-auto —— 已合并

评估

难度
3/5
预计耗时
1-2 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
node.js, rust
领域
distributed-systems

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Rust
星标
226
派生
62
平均合并
20 小时 46 分钟
30 天内合并 PR
6

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/duroxide 的其他 Issue

查看 microsoft/duroxide 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。