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

Open
#257 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the load_sbom pipeline and the create_dependecies handling referenced in the issue, using a minimal SBOM once reproducible input is available. Trace how an imported dependency is resolved and persisted, then verify that self-referential relationships are rejected appropriately and repeated imports do not create duplicate dependency entries.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
53
Forks
32
Avg merge
16h 44m
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/dejacode

All issues in aboutcode-org/dejacode

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.