Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

BUG: SBOM import fails with "The 'for_package' cannot be the same as 'resolved_to_package'" and duplicates number of dependencies

未关闭
#257 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
backend

调研方向

从 load_sbom pipeline 和 issue 中引用的 create_dependecies 处理开始,在有可复现输入后使用一个最小 SBOM。跟踪导入的依赖项是如何解析并持久化的,然后验证自引用关系会被适当地拒绝,且重复导入不会创建重复的依赖项条目。

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

描述

bug design needed enhancement PackageSet

Describe the bug
When importing a particular SBOM created with cdxgen, the load_sbom pipeline succeeds according to ScanCode.io, but DejaCode reports issues importing the dependencies. The error message states: The 'for_package' cannot be the same as 'resolved_to_package'

Repeating the SBOM import causes an additional issue. DejaCode duplicates the number of dependencies, apparently not realizing that these are the same dependencies that have been previously added.

Note: This is the same SBOM as https://github.com/aboutcode-org/scancode.io/issues/1576 where ScanCode reported issues with create_dependecies but the overall pipeline is considered a success.

To Reproduce
Not clear yet. Cannot share actual data at the moment. I will see if an MWE can be provided.
If the error provides indication what I should look out for in the SBOM, I might be able to find it quicker.

Expected behavior
The SBOM should be properly loaded and no duplicate dependency entries should be added

Screenshots
Image

Context (OS, Browser, Device, etc.):
n.a.

主要语言
Python
星标
52
派生
30
平均合并
4 小时 57 分钟
30 天内合并 PR
21

环境准备

从这里开始

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

aboutcode-org/dejacode 的其他 Issue

查看 aboutcode-org/dejacode 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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