Closed cody-scott closed 2 months ago
We suspect pydantic 2.9.0 rolling out a couple of hours ago as the root cause. Adding a pydantic<2.9.0
pin to your dependencies is the workaround. We will add this pin in the upcoming 1.8.5 release of Dagster.
Same issue with 1.8.4. Pinning to less then 2.9 was my fix too. Thanks!
thanks @garethbrickman appreciate the quick turn around!
Quick Work pinning to <2.9 made our instance boot again!
pydantic<2.9.0
worked for me as well.
Thanks for this issue, this was driving me crazy π
Dagster version
1.7.15
What's the issue?
After the recent pydantic update, dagster is throwing errors related to the Dagster DBT package
What did you expect to happen?
Dagster to start successfully
How to reproduce?
install
pydantic=2.9.0
with the dagster 1.7.15. An unpinned install should pull the latest 2.9.0 versionDeployment type
Docker Compose
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a π! We factor engagement into prioritization.