Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Import Memory Handling: Do not maintain parsed findings long term #12106

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

Merged
merged 1 commit into from
Mar 26, 2025

Conversation

Maffooch
Copy link
Contributor

When processing many imports at once, it was noticed that memory of the redis container was maintaining a very high level. This is because the findings parsed from the submitted report were being saved on the Importer class, and in scope for the entire duration of the process. We should not maintain the list of parsed findings after they have been consumed

[sc-10595]

Copy link

DryRun Security Summary

The code underwent a refactoring process to simplify parsing methods, remove redundant attributes, and improve overall code structure for default importer and reimporter classes without introducing any security vulnerabilities.

Expand for full summary
  1. Summary: Refactoring of default importer and reimporter classes to simplify parsing methods, remove redundant instance attributes, and optimize code structure.

  2. Security Findings:

  • No security vulnerabilities found.

View PR in the DryRun Dashboard.

Copy link
Contributor

@mtesauro mtesauro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@mtesauro mtesauro merged commit 3fa721a into DefectDojo:bugfix Mar 26, 2025
76 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants