You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The on run end we are running to upload dbt_artifacts in all our jobs are failing on the upload sources command with the error "Object of type date is not JSON serializable". This is causing all our jobs to fail.
In our jobs we then have a --vars '{"run_post_hook": "on"}' in the command. This has been working fine for 6+ months. The failures started four days ago (with no code changes made by us).
alvawinsa
changed the title
[Bug]: Object of type date is not JSON serializable
[Bug]: Object of type date is not JSON serializable (Databricks)
Aug 26, 2024
Overview
The on run end we are running to upload dbt_artifacts in all our jobs are failing on the upload sources command with the error "Object of type date is not JSON serializable". This is causing all our jobs to fail.
How to reproduce
We are using dbt cloud with
version: 2.6.2
Running on the Databricks connection.
on-run-end:
In our jobs we then have a --vars '{"run_post_hook": "on"}' in the command. This has been working fine for 6+ months. The failures started four days ago (with no code changes made by us).
Expected behaviour
I expect this:
0:02:04 Uploading model executions
00:02:04 Uploading seed executions
00:02:04 Uploading test executions
00:02:04 Uploading snapshot executions
00:02:08 Uploading exposures
00:02:10 Uploading seeds
00:02:13 Uploading snapshots
00:02:15 Uploading invocations
dbt command failed00:02:18 Uploading sources
00:02:20 Uploading tests
00:02:20 Database error while running on-run-end
To also Upload source successfully.
Screenshots
Nothing that can contribute anything else.
Environment
Results of running
dbt --version
: versionless# Add the results here
Please paste the contents of your
packages.yml
file here:packages:
version: 0.10.0
version: 1.1.1
version: 0.9.0
version: 0.9.0
version: 2.6.2
The text was updated successfully, but these errors were encountered: