t-rust: Source repo comparison flags auxiliary repo directories as "source_repo_only"
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by locating the Rust source repository comparison code and the tests that produce source_repo_only results; the issue does not name specific files. Trace how crate contents and Cargo.toml include/exclude rules affect comparison, using the syn example as a reference. Done means auxiliary directories omitted from the published crate no longer appear as mismatches, while real repository differences remain reported.
由索引模型根据 Issue 内容生成。
描述
Reference: https://github.com/aboutcode-org/scancode.io/issues/1767#issuecomment-4051759506
When a Rust crate lives at the repository root, the source repo comparison reports every file in directories that exist in the repo but are not shipped in the published crate — such as benches/, dev/, ci/, fuzz/, examples/, tests/, assets/ — as source_repo_only mismatches.
These are not actual discrepancies. They are auxiliary directories that are present in the upstream repository but stripped from the published crate tarball (or excluded by the crate's Cargo.toml include/exclude rules).
Sample:
syn at the repo root, https://github.com/dtolnay/syn/tree/2.0.117, has benches/, dev/, ci/, .github/ alongside the crate source. Comparing the published syn crate against its repo archive currently produces a source_repo_only list with dozens of entries, all noise.
source_repo_only should list only real differences between the repository and the published crate, not auxiliary directories.
- 主要语言
- Python
- 星标
- 223
- 派生
- 214
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 13
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aboutcode-org/scancode.io 的其他 Issue
-
ignored_dependency_scopes does not exclude npm devDependencies可能已有人在做 @MGpromax 于 64 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
aboutcode-org/scancode.io#2215 ·
维护者通常 1 天内回复
-
Delivery Error in scan_single_package: No connection adapters were found for '/notifications/send_scan_notification/可能重新可做 @akshat-lakhera 于 11 天前认领，目前没有进行中的 PR。 未关闭bug
难度 2/5 1-3 小时 新手友好度 70/100
aboutcode-org/scancode.io#2206 · 1 条评论 ·
维护者通常 1 天内回复
-
update `run` cli command to run pipelines without an input可能已有人在做 @NoiceHax 于 76 天前认领。 未关闭nice-to-have
难度 2/5 1-3 小时 新手友好度 72/100
aboutcode-org/scancode.io#2203 · 1 条评论 ·
维护者通常 1 天内回复
-
Local developement docs are outdated可能已有人在做 @nik-767 于 106 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 82/100
aboutcode-org/scancode.io#2197 · 1 条评论 ·
维护者通常 1 天内回复
-
maven-heaven: `map_shaded_classes_to_maven_packages` ignores POMs present only in the from/ codebase, leaving all shaded .class resources unmapped可能已有人在做 @chinyeungli 于 2 天前认领。 未关闭
aboutcode-org/scancode.io#2284 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 aboutcode-org/scancode.io 的全部 Issue
相似的 Issue
-
getchaintips leaves out the active tip once a header is staged on it, where Core always lists it未关闭
难度 2/5 1-3 小时 新手友好度 88/100
btclib-org/btclib-node#2158 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
dbt-msft/dbt-sqlserver#897 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
Gathin23/cleanyourtv#2770 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
vllm-project/vllm#64845 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
dekobon/big-code-analysis#1729 ·
维护者通常 1 天内回复