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

Fix failing analysis updates #769

Merged
merged 2 commits into from
Jul 2, 2024
Merged

Conversation

nscuro
Copy link
Member

@nscuro nscuro commented Jul 2, 2024

Description

Fixes invalid stream header exception when modifying analyses with associated vuln policy.

When an existing analysis, which is assigned to a vulnerability policy, was updated, DataNucleus failed with invalid stream header. This happened because, when updating an analysis, DataNucleus fetches all associated objects, which includes VulnerabilityPolicy.

The VulnerabilityPolicy class does not map cleanly to the database schema: Some fields use PostgreSQL-native arrays, others use JSONB.

It also turned out that the model class isn't really used anywhere, since we modify and query VulnerabilityPolicy via JDBI. Hence the class was removed entirely, replacing it with a simple ID column of type Long.

Also fixes vuln policy assignment getting lost upon project cloning.

Addressed Issue

N/A

Additional Details

N/A

Checklist

  • I have read and understand the contributing guidelines
  • This PR fixes a defect, and I have provided tests to verify that the fix is effective
  • This PR implements an enhancement, and I have provided tests to verify that it works as intended
  • This PR introduces changes to the database model, and I have updated the migration changelog accordingly
  • This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

nscuro added 2 commits July 2, 2024 15:54
…uln policy

When an existing analysis, which is assigned to a vulnerability policy, was updated, DataNucleus failed with `invalid stream header`. This happened because, when updating an analysis, DataNucleus fetches all associated objects, which includes `VulnerabilityPolicy`.

The `VulnerabilityPolicy` class does not map cleanly to the database schema: Some fields use PostgreSQL-native arrays, others use JSONB.

It also turned out that the model class isn't really used anywhere, since we modify and query `VulnerabilityPolicy` via JDBI. Hence the class was removed entirely, replacing it with a simple ID column of type `Long`.

Signed-off-by: nscuro <[email protected]>
@nscuro nscuro added the defect Something isn't working label Jul 2, 2024
@nscuro nscuro added this to the 5.5.0 milestone Jul 2, 2024
Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.16% (target: -1.00%) 100.00% (target: 70.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (919a8ce) 20677 16882 81.65%
Head commit (8ec0a06) 20641 (-36) 16885 (+3) 81.80% (+0.16%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#769) 3 3 100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences


🚀 Don’t miss a bit, follow what’s new on Codacy.

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

@nscuro nscuro merged commit 974eb9c into main Jul 2, 2024
9 checks passed
@nscuro nscuro deleted the fix-makeanalysis-with-vulnpolicy branch July 2, 2024 14:51
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
defect Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants