Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audit vulnerabilities not showing records of big projects #3970

Closed
2 tasks done
Pabloo-ss opened this issue Jul 12, 2024 · 4 comments
Closed
2 tasks done

Audit vulnerabilities not showing records of big projects #3970

Pabloo-ss opened this issue Jul 12, 2024 · 4 comments
Labels
duplicate This issue or pull request already exists

Comments

@Pabloo-ss
Copy link

Current Behavior

When uploading large SBOMs and accessing audit vulnerabilities inside the project, "No matching records found" is displayed although project has many vulns.
image

Steps to Reproduce

  1. Upload large SBOM
  2. Go to audit vulnerabilities inside the project
  3. "No matching records found" is displayed
    go_sbom.json

Expected Behavior

Display all vulns.
The rest of the projects, which are quite smaller display vulns correctly, except another project which is also quite large and undergo the same problem (both projects are SBOM of root level manifests in monorepo: pnpm-lock.yaml and go.mod)

Dependency-Track Version

4.11.5

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

No response

Browser

Google Chrome

Checklist

@Pabloo-ss Pabloo-ss added defect Something isn't working in triage labels Jul 12, 2024
@nscuro
Copy link
Member

nscuro commented Jul 12, 2024

Can you please check the Console and Network tabs in your browser's developer tools? Any errors or failing / slow requests when you click Refresh on the findings table?

Based on your screenshot I'm inclined to say the request for fetching findings is timing out.

There are some quite significant performance improvements coming for this in v4.12: #3869

@Pabloo-ss
Copy link
Author

You are right, Im getting a 504. I suppose Ill have to wait until v4.12 is released... Thank you!!

@nscuro nscuro added duplicate This issue or pull request already exists and removed defect Something isn't working pending more information labels Jul 16, 2024
@nscuro
Copy link
Member

nscuro commented Jul 16, 2024

Thanks, I'll close this as duplicate of #3811 then.

@nscuro nscuro closed this as not planned Won't fix, can't repro, duplicate, stale Jul 16, 2024
Copy link
Contributor

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants