Display issues with the ingested data #225

New issue

Open

opened 2024-09-27 01:21:49 +00:00 by fricklerhandwerk · 2 comments

fricklerhandwerk commented

2024-09-27 01:21:49 +00:00

(Migrated from github.com)

As a developer of the security tracker backend, I want to know which errors or inconsistencies there are with the data it is processing. This way we can fix the code or do something about the data.

Examples of Nixpkgs data issues: https://github.com/Nix-Security-WG/nix-security-tracker/issues/57

Store error logs and for each data source and display them in the admin view.

As a developer of the security tracker backend, I want to know which errors or inconsistencies there are with the data it is processing. This way we can fix the code or do something about the data. Examples of Nixpkgs data issues: https://github.com/Nix-Security-WG/nix-security-tracker/issues/57 Store error logs and for each data source and display them in the admin view.

RaitoBezarius commented

2024-10-04 13:41:17 +00:00

(Migrated from github.com)

1st usecase:

AffectedProductDataProblem:

Once ingesting an affected product, if there's any CPEs attached to it, we want to verify the coherence between the WFN and the data in the affected product model.

If there's any issue, just save a model with the type of error for admins.

1st usecase: ``` AffectedProductDataProblem: Once ingesting an affected product, if there's any CPEs attached to it, we want to verify the coherence between the WFN and the data in the affected product model. If there's any issue, just save a model with the type of error for admins. ```

fricklerhandwerk commented

2024-11-29 12:25:53 +00:00

(Migrated from github.com)

These packages are currently filtered out, likely for having >1000 matches, but they shouldn't have that many:

These packages are currently filtered out, likely for having >1000 matches, but they shouldn't have that many: ![image](https://github.com/user-attachments/assets/6afeb800-375f-4a2d-97cf-2c9ad996cdcc)