Hey Is dagster cli having a package issue? Pods ar...
# ask-community
t
Hey Is dagster cli having a package issue? Pods are in crashback loop due to this error about a removed type in the pydantic library
🤖 1
j
I just ran into this in a test env that was working fine before, and it turned out the update to pydantic v2 was a problem. we are using dagster 1.3.10, which doesn’t specify pydantic < v2
So adding pydantic==1.* ahead of dagster in our requirements fixed the issue for us
but it looks like later versions of dagster specify pydantic < 2 so that should also fix this?
I was actually about to ask this same question before we figured it out, so I’m not the foremost authority on any of that.
t
gotcha, thanks Jake! Our teams gonna migrate to poetry to fix this pinning
j
FWIW https://docs.pydantic.dev/latest/blog/pydantic-v2-final/ blog post announcing v2 release dated today.
gotcha, thanks Jake! Our teams gonna migrate to poetry to fix this pinning
We’ve also been eying poetry as well. 😄
b
at the moment we’ve pinned
pydantic<2
on our newer versions of Dagster as we’re working on compatibility with pydantic v2 - if you’re using an older build and able to pin pydantic that should hopefully fix this issue
❤️ 4
t
amazing, thanks for the quick response time ❤️