DependencyTrack / DependencyTrack/dependency-track

Finding API crashing when is expected to return a very large amount of data

Open
#4,730 5 comments 0 reactions 0 assignees View on GitHub
defect in triage
Dominant language
Java
Stars
4.2k
Forks
811
Avg merge
8h 39m
Merged PRs (30d)
237

Description

### Current Behavior

Hi Steve, I am using finding api: "/api/v1/finding?severity=critical,high&pageSize=23029&pageNumber=1" to collect all findings for a lot of repositories, I am filtering with only the data that I need but the api is not returning a such amount of large data, is that a known issue or should I take another approach ?

### Steps to Reproduce

Call the finding api with a json that have a huge amount of findings

### Expected Behavior

The api will crash due to large size

### Dependency-Track Version

4.12.6

### Dependency-Track Distribution

Executable WAR, Container Image

### Database Server

PostgreSQL

### Database Server Version

_No response_

### Browser

Google Chrome

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.