External refresh edge cases: capture failure and lease after error

未关闭
#2,696 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
backend

调研方向

Start by reading the implementation and tests for Record writes, capture failure handling, claim_plan, and batch refresh attempts; the issue does not name their files. Trace how a failed capture affects reconciliation, how errors release a plan lease, and whether one failing target blocks its batch. Done means each edge case has defined behavior and regression coverage; the desired behavior is not specified here.

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

描述

  • When capture fails inside a Record write, BReg rolls back to the savepoint, logs a warning and commits the write. It does not mark the plan for reconciliation, so a changed link key waits a full interval.
  • An error after claim_plan holds the plan lease until it expires.
  • A target that always fails fails its whole batch, up to the attempts ceiling.

All three are low severity. The last two may predate the in-process worker.

Deferred from #2693.

主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

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

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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