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: higher default timeout for database download #2033

Merged
merged 1 commit into from
Aug 9, 2024

Conversation

willmurphyscode
Copy link
Contributor

Depending on region and network conditions, 120s was not enough time for many clients, leading to some complaints. Raise the default timeout to five minutes.

There's an open question whether we should wait for more data from the latest attempt to resolve the CDN issues

Fixes #1885

@willmurphyscode willmurphyscode self-assigned this Aug 5, 2024
@willmurphyscode willmurphyscode added database Relating to the grype DB asset performance labels Aug 5, 2024
Depending on region and network conditions, 120s was not enough time for
many clients, leading to some complaints. Raise the default timeout to
five minutes.

Signed-off-by: Will Murphy <willmurphyscode@users.noreply.github.com>
@willmurphyscode willmurphyscode force-pushed the fix-higher-default-db-timeout branch from 76f8b01 to dad653c Compare August 6, 2024 11:49
@spiffcs
Copy link
Contributor

spiffcs commented Aug 8, 2024

Separately, the DataDog synthetics are telling us that the default timeout for downloading the new database, 2 minutes, is definitely too low for some regions and networks, so I’ll raise that, probably to 5 minutes.

Given the above comment from discourseI think this is ok to merge now.

I've approved this @willmurphyscode but left it to you to merge if you're looking to wait for any more data 👍

@willmurphyscode willmurphyscode merged commit f9b6365 into main Aug 9, 2024
10 checks passed
@willmurphyscode willmurphyscode deleted the fix-higher-default-db-timeout branch August 9, 2024 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database Relating to the grype DB asset performance
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Grype failed to load vulnerability database: database metadata not found
2 participants