-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[Bug] dbt deps should keep retrying if registry response is None #4178
Comments
It does look like we get a response here:
but that it's potentially empty or malformed, leading to response = None. Do we need to check for an empty response and retry in that case as well? |
@crystalro0 Thanks for the report! @barberscott Your read here seems right on. It's reasonable to expect that dbt should continue retrying until it returns a response that isn't I think the change for that should happen somewhere in the weeds of |
Hi! I'd be happy to work on this one unless @barberscott wants to create a PR himself. |
Allow retries when the answer is None
Allow retries when the answer from dbt deps is None
Is there an existing issue for this?
Current Behavior
Running dbt deps in a nightly job failed after retrying downloading the packages. The Max retries is listed as 5 and was currently at 0.
Expected Behavior
The download is retried until the max retries is reached or the package is downloaded successfully.
Steps To Reproduce
This cannot be reproduced on demand. It is an intermittent failure case for
dbt deps
Relevant log output
Environment
- dbt: 0.21.0
What database are you using dbt with?
snowflake
Additional Context
No response
The text was updated successfully, but these errors were encountered: