DependencyTrack / DependencyTrack/frontend

affectedProjects tab false negatives on API error

Open
#1,080 1 comment 0 reactions 0 assignees View on GitHub
defect p2 size/S
Dominant language
Vue
Stars
171
Forks
250
Avg merge
10h 56m
Merged PRs (30d)
84

Description

### Current Behavior

`https://deptrack.com/vulnerabilities/GITHUB/GHSA-x8vp-gf4q-mw5j/affectedProjects`

Which performs a request to

`https://deptrack.com/api/v1/vulnerability/source/GITHUB/vuln/GHSA-x8vp-gf4q-mw5j/projects?excludeInactive=true&searchText=`

When the API returns a (500) error upon retrieving the `affectedProjects` for a `Vulnerability`, there is no indication of the error and the `affectedProjects` tab remains empty (`0`).

![Image](https://github.com/user-attachments/assets/cc7bc599-be0f-415e-8f87-c349ac74d24e)

### Steps to Reproduce

This only happens when the API returns an error, in my case it was cause by 1 or more projects having the `ACTIVE` column set to `NULL`.

### Expected Behavior

Some feedback about the error.

### Dependency-Track Frontend Version

4.12.1

### Browser

Google Chrome

### Browser Version

latest

### Operating System

Windows

### 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/frontend/issues) for whether this defect was already reported

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.