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

Change: Encode CPE match strings directly to file #61

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

timopollmeier
Copy link
Member

What

The JSON downloader for CPE match strings now writes the encoded chunks of the JSON dict directly to the output file and only buffer it in memory if validation is requested.

Why

This reduces the amount of memory used for creating the output file after the data has been downloaded from the API.

References

GEA-820

Checklist

  • Tests

@timopollmeier timopollmeier requested review from a team as code owners January 10, 2025 11:12
@greenbonebot greenbonebot enabled auto-merge (rebase) January 10, 2025 11:12
Copy link

Conventional Commits Report

Type Number
Changed 1

🚀 Conventional commits found.

The JSON downloader for CPE match strings now writes the encoded
chunks of the JSON dict directly to the output file and only
buffer it in memory if validation is requested.

This reduces the amount of memory used for creating the output file
after the data has been downloaded from the API.
@timopollmeier timopollmeier force-pushed the encode-matches-to-file branch from 1df2a47 to 17b28d0 Compare January 10, 2025 11:16
@greenbonebot greenbonebot merged commit 40ab3ab into main Jan 10, 2025
11 checks passed
@greenbonebot greenbonebot deleted the encode-matches-to-file branch January 10, 2025 11:31
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.

3 participants