lib/yaml-subset.awk keeps the first duplicate key where the CI parser rejects the file
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 54/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 領域
- build-system, testing
研究方向
Read lib/yaml-subset.awk and trace how --strict is passed by parse-concern-value.sh; inspect scripts/shared-copies.txt and the consumers of non-strict mode. Add duplicate-key rejection for keys in the same mapping in strict mode, propagate the canonical change with bash scripts/sync-shared-copies.sh, and check that non-strict consumers retain their current behavior. Done means strict mode rejects the duplicate case while existing non-strict behavior is preserved.
由索引模型根據 Issue 內容生成。
描述
Problem
When a mapping repeats a key, the shared awk YAML reader lib/yaml-subset.awk keeps the first value. The CI config parser rejects the same file. So a local reader and CI can disagree about one config.
Concrete case: babysit_merge_policy.py reads docs/conventions/pr-pipeline.yaml through this reader (via parse-concern-value.sh --strict) to decide the unattended merge rung. If the merge: block contained a key twice, CI would reject the file but the local reader would act on the first value. The CI rejection keeps the bad config off main, so this is latent today.
Expected
--strict mode treats a duplicate key in the same mapping as a parse error, the same as the CI parser.
Scope
- Canonical source:
lib/yaml-subset.awk. - Copies registered in
scripts/shared-copies.txt(16 files on main); propagate withbash scripts/sync-shared-copies.sh. - Check each consumer of the non-strict mode keeps its current behavior, or opt it in.
Related
- #6699: the Python
yaml_subset.pyreports the wrong line for a duplicate key in a sequence item. It is a separate reader. - #6202: auto-merge-safe-prs. Found by the Phase 8 security review on #7324.
🤖 Generated with Claude Code
- 主要語言
- Shell
- 星號
- 22
- 分支
- 2
- 平均合併
- 8 小時 24 分鐘
- 30 天內合併 PR
- 947
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
melodic-software/claude-code-plugins 的其他 Issue
-
needs-human needs-triage priority: medium
難度 2/5 1-3 小時 新手友好度 65/100
melodic-software/claude-code-plugins#7455 · 1 則留言 ·
維護者通常 1 天內回覆
-
priority: medium
難度 2/5 1-3 小時 新手友好度 68/100
melodic-software/claude-code-plugins#7351 · 2 則留言 ·
維護者通常 1 天內回覆
-
agent-ready priority: high work-class: scoped
難度 2/5 1-3 小時 新手友好度 74/100
melodic-software/claude-code-plugins#7312 · 3 則留言 ·
維護者通常 1 天內回覆
-
priority: medium
難度 2/5 1-3 小時 新手友好度 76/100
melodic-software/claude-code-plugins#7288 · 2 則留言 ·
維護者通常 1 天內回覆
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail threshold未關閉needs-human
難度 2/5 1-3 小時 新手友好度 78/100
melodic-software/claude-code-plugins#7286 · 2 則留言 ·
維護者通常 1 天內回覆
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
bug needs-triage
難度 1/5 1 小時以內 新手友好度 78/100
mattpocock/skills#1281 ·
維護者通常 1 天內回覆
-
github_actions
難度 2/5 1-3 小時 新手友好度 62/100
hiero-ledger/hiero-consensus-node#27621 ·
維護者通常 1 天內回覆
-
application-issue
難度 2/5 1-3 小時 新手友好度 72/100
Installomator/Installomator#3427 ·
維護者通常 3 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
software-mansion/argent#1483 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100