Skip to content
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]: Runtime error since migration to dbt 1.9 (Object of type datetime is not JSON serializable) #480

Open
D1111111 opened this issue Feb 7, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@D1111111
Copy link

D1111111 commented Feb 7, 2025

Overview

Error during dbt compile after I migrated from 1.8.2 to 1.9.0 dbt.

dbt_artifacts version: 2.8.0
Image

How to reproduce

  1. Migrate dbt to the latest version 1.9.0
  2. Run dbt compile
  3. An error is raised
2:57:33  Encountered an error:
Runtime Error
  Compilation Error in operation confirmation_transformation_dw-on-run-end-0 (.\dbt_project.yml)
    Object of type datetime is not JSON serializable
    > in macro upload_models (macros\upload_individual_datasets\upload_models.sql)
    > called by macro get_table_content_values (macros\upload_results\get_table_content_values.sql)
    > called by macro upload_results (macros\upload_results\upload_results.sql)
    > called by operation confirmation_transformation_dw-on-run-end-0 (.\dbt_project.yml)

Expected behavior

Screenshots

Environment

Results of running dbt --version:

Core:
  - installed: 1.9.2
  - latest:    1.9.2 - Up to date!

Plugins:
  - postgres: 1.9.0 - Up to date!

Please paste the contents of your packages.yml file here:

packages:
  - package: dbt-labs/dbt_utils
    version: 1.3.0

  - package: dbt-labs/codegen
    version: 0.13.1

  - package: calogica/dbt_expectations
    version: 0.10.4

  - package: calogica/dbt_date
    version: 0.10.1

  - package: brooklyn-data/dbt_artifacts
    version: 2.8.0
@D1111111 D1111111 added the bug Something isn't working label Feb 7, 2025
@D1111111
Copy link
Author

This may be related to microbatches loading strategy since I use it, and that was the reason for migration to 1.9.

Might be related to this bug: #476

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant