-
Notifications
You must be signed in to change notification settings - Fork 503
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_utils.date_spine gives Python error #873
Comments
hazvk
changed the title
[Bug] <title>
[Bug] dbt_utils.date_spine is not working as expected
Mar 8, 2024
hazvk
changed the title
[Bug] dbt_utils.date_spine is not working as expected
[Bug] dbt_utils.date_spine gives error when using legitimately
Mar 8, 2024
hazvk
changed the title
[Bug] dbt_utils.date_spine gives error when using legitimately
[Bug] dbt_utils.date_spine gives Python error
Mar 8, 2024
Wondering if there is an update on the issue? |
I run into the same error, also databricks 1.7.0 and dbt-core 1.7.14 |
I got the issue but it's working after upgrade. My versions:
|
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Issue still valid |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a new bug in dbt-core?
Current Behavior
Running this model and using
dbt_utils.date_spine
used to work. I now get an error I can't get to the bottom of.Expected Behavior
Should evaluate and give a table
Steps To Reproduce
With dbt on local machine:
dbt build -f
Relevant log output
Environment
Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
Using dbt-databricks==1.6.8
Last seen working on Jan 24th. Then another issue came up that I only just resolved, per issue (and hence why I fixed version of
databricks-sdk
). I haven't tested this functionality until yesterday, which is when I first noticed it was broken.The text was updated successfully, but these errors were encountered: