-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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-473] [Bug] dbt deps still can fail with 'NoneType' object is not subscriptable
#5023
Comments
'NoneType' object is not subscriptable
'NoneType' object is not subscriptable
Thanks for the report @barberscott! I'm trying to wrap my head around how, if dbt-core/core/dbt/clients/registry.py Lines 54 to 90 in 5852f17
Ideally, that exception would trigger a retry; at the very least, it should be the exception we see in the stacktrace, rather than the surprise at trying to resolve Accessing the raw logs may give a better sense of the narrative, for exactly which steps succeeded in the leadup to the |
I poked through the code too and didn't see how that could happen. At the very least, we should check for |
I do wonder if we should catch all exceptions in connection_exception_retry. We're only catching RequestException and ReadError. Should we also add a catch of Exception? Not catching an exception there shouldn't cause this error as far as I can tell, but just to make sure there's not something we're missing... |
Reopening since it looks like, darn, we didn't catch this! A recent dbt run failed on v1.0.5 with the following error:
|
Is there an existing issue for this?
Current Behavior
It appears that there is still an exception that the current code is not catching on v1.0.5-rc2 -- this one is new!
so something else is sneaking through.
Expected Behavior
The root cause of this error is caught, logged, and the download retried.
Steps To Reproduce
No response
Relevant log output
No response
Environment
- dbt: 1.0.5-rc2 (dbt Cloud)
What database are you using dbt with?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: