-
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
[CT-77] [Bug] dbt deps should keep retrying if registry response is malformed (bug regression) #4601
Comments
Thanks for the report @BrJan! This issue is a duplicate of #4577 that was recently reported. The log output for each is a bit different but in both we're hitting a bug here: dbt-core/core/dbt/clients/registry.py Lines 36 to 39 in 7798f93
I'm going to close this issue as a duplicate. We're targeting the next release for a fix for this. |
Backport: #4649 |
Turns on v1.0.3 did not fix this variant of the failure:
|
Another variation on the same theme:
|
Goal: Let's confirm if we are retrying like expected? If not, why not? |
We are not retrying for these cases. After looking through some logs, I'm seeing three exceptions thrown that we are not catching.
These need to be added to the list of exceptions to catch and retry. Lines 609 to 613 in ecfd77f
Alternatively we could catch all exceptions from Requests by catching just |
Just to confirm - we're planning to close this one in favor of / by means of #4849? |
Since that task mentions this one and has all the details to hopefully fix this issue, yes. |
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: 1.0.1
What database are you using dbt with?
snowflake
Additional Context
This is a regression of #4178.
The text was updated successfully, but these errors were encountered: