Build outputs shared by several languages are reported under one of them; outputs of a build system hide the language-wide ones
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 40/100
调研方向
Start by reading outputs_of in facts/outputs.py and tracing how CommittedOutput facts are grouped for reporting. Compare the BEAM and JVM cases described in the issue, including tests/fixtures/bare_beam. Decide whether shared outputs should be reported under each owning language or once per ecosystem, and whether build system outputs should add to language wide outputs; done means both behaviors are covered by clear, consistent results.
由索引模型根据 Issue 内容生成。
描述
committed-artifacts and vcs-ignore answer per language, and a BuildOutput of several languages is reported under one of them. BEAM's _build/ and erl_crash.dump are outputs of both Elixir and Erlang; in tests/fixtures/bare_beam (both languages) the check says
Elixir: no build outputs are committed; Erlang: 2 build outputs are committed
although the committed _build/ is Elixir's too (JVM's shared outputs behave the same for Java and Kotlin). The CommittedOutput fact carries every language; it is the answer's grouping that picks one. An output shared by the languages of one ecosystem would read better reported once, under the ecosystem, or under every language that owns it.
Related: outputs_of (facts/outputs.py) returns the outputs tied to the build systems in use or, only when none is, the language-wide ones. A profile that ties one output to a build system therefore hides its language-wide outputs for that build system (BEAM had to leave deps/ untied so _build/ still counted for Elixir; JVM's *.class output is hidden whenever Maven or Gradle is used). Is that precedence intended, or should the two sets add up?
🤖 Generated with Claude Code
- 主要语言
- Python
- 星标
- 4
- 派生
- 1
- 平均合并
- 10 小时 41 分钟
- 30 天内合并 PR
- 79
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
cpp-best-practices/project_validator 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
cpp-best-practices/project_validator#267 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
cpp-best-practices/project_validator#263 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
cpp-best-practices/project_validator#260 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
cpp-best-practices/project_validator#259 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
cpp-best-practices/project_validator#255 ·
维护者通常 1 天内回复
查看 cpp-best-practices/project_validator 的全部 Issue
相似的 Issue
-
plot_graph crashes when a mesh node has no m2m edge可能已有人在做 @tygvi 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
mllam/neural-lam#883 · 1 条评论 ·
维护者通常 2 天内回复
-
enhancement possible-duplicate
难度 1/5 1-3 小时 新手友好度 78/100
AOSSIE-Org/PictoPy#1715 · 2 条评论 ·
维护者通常 6 天内回复
-
SQLite connector omits generated columns from the catalog, and drops relationships sourced on them未关闭
难度 2/5 1-3 小时 新手友好度 72/100
NVIDIA/auto-ontology#511 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
ethereum/execution-specs#3996 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
Project-N-E-K-O/N.E.K.O#3725 ·
维护者通常 1 天内回复