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 infinite recursion during policy condition serialization #4165

Merged

Conversation

nscuro
Copy link
Member

@nscuro nscuro commented Sep 22, 2024

Description

Fixes infinite recursion during policy condition serialization.

Addressed Issue

N/A

Additional Details

As of Alpine v3, objects are no longer unloaded and refreshed (with fetch groups) during QueryManager#persist.

In case of the PolicyCondition REST endpoints, the previous behavior caused PolicyCondition#policy to be unloaded, prior to serializing the PolicyCondition response.

With persistent objects no longer being unloaded and refreshed in QueryManager#persist, that behavior changed, leading to infinite recursion when serializing PolicyCondition#policy.

Resolved the issue by restoring the previous behavior of not returning policy data in any of the condition endpoints.

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 added corresponding update logic
  • This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

As of Alpine v3, objects are no longer unloaded and refreshed (with fetch groups) during `QueryManager#persist`.

In case of the `PolicyCondition` REST endpoints, the previous behavior caused `PolicyCondition#policy` to be unloaded, prior to serializing the `PolicyCondition` response.

With persistent objects no longer being unloaded and refreshed in `QueryManager#persist`, that behavior changed, leading to infinite recursion when serializing `PolicyCondition#policy`.

Resolved the issue by restoring the previous behavior of not returning policy data in any of the condition endpoints.

Signed-off-by: nscuro <nscuro@protonmail.com>
@nscuro nscuro added the defect Something isn't working label Sep 22, 2024
@nscuro nscuro added this to the 4.12 milestone Sep 22, 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 (43e73d9) 21952 17280 78.72%
Head commit (3c3b2ae) 21956 (+4) 17319 (+39) 78.88% (+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 (#4165) 5 5 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

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

@nscuro nscuro merged commit 237ba91 into DependencyTrack:master Sep 22, 2024
11 checks passed
@nscuro nscuro deleted the fix-policycondition-serialization branch September 22, 2024 14:22
nscuro added a commit to DependencyTrack/hyades-apiserver that referenced this pull request Sep 22, 2024
Ports DependencyTrack/dependency-track#4165 from Dependency-Track v4.12.0

Signed-off-by: nscuro <nscuro@protonmail.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 23, 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.

1 participant