feat(reconciler): 阶段 3 控制类动作——worker fenced CAS 通道（#321 留续，候 #322 已落可启）
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 43/100
Research direction
Read the reconciler work in #321, the ownership implementation in #322, and the #316 snapshot flow to locate the shadow difference handling and worker fenced CAS channel. Start by tracing how shadow differences are reported and how ownership v1 performs fenced CAS. Done means the control action tests pass for replenishing a carrier and terminalizing work, while shadow mode remains read-only and the snapshot source is unchanged.
Written by the indexing model from the issue text.
Description
优先级 P3 · depends-on: 无（#322 所有权 v1 已合 d61a038a，fenced CAS 通道在位）
来源：A1 r138 评审 + B3 r102 交付注记（#321 shadow 阶段收官，控制类动作显式留阶段 3）。
Summary
#321 载体对账器 shadow 阶段已合 main（d52e2eed：expected 按状态×pending.kind 推导×#316 四存放处快照，差异四格 gauge+custody 判据）。本单=阶段 3：shadow 发现差异后的控制类动作接入——复用 worker fenced CAS 通道（#322 所有权 v1 已落）执行补载体/终态化，替代纯观测。
验收
shadow 差异→fenced CAS 控制动作格先红后绿；只读纪律在 shadow 模式下保持；#316 快照同源不破坏。
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jeffkit/plaita
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 43/100
jeffkit/plaita#345 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
bug P1
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Toloka/tolokaforge#1947 ·
Maintainers usually reply within 1 day
-
SageMaker provider: streaming fails with NoStreamDataError on DJL Serving (LMI) endpointsPossibly taken @balajiaru claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
UKGovernmentBEIS/inspect_ai#6127 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
pydot/pydot#601 · 4 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
letsencrypt/cp-cps#361 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100