Hello team, We are facing sqlalchemy issue while we are using Dagster through helm install. Can someone help how to limit sqlalchemy version when we use Dagster through helm? Thanks!

Hi! Which dagster version are you installing?

Thanks for the fast response! Yeah we added newest ver, dagster==1.1.14 to be installed through Docker (and checked the version on the image) then deploy for using in Dagster, but having no luck yet..

Hi wonjae, where exactly are you seeing the error?

Hey Daniel - not a huge deal as I’ll just roll back, but I updated to 1.1.14 and I’m seeing the same stack trace as earlier:

sqlalchemy.exc.ArgumentError: Column expression, FROM clause, or other columns clause element expected, got [Column('run_body', Text(), table=<runs>), Column('status', String(length=63), table=<runs>)]. Did you mean to say select(Column('run_body', Text(), table=<runs>), Column('status', String(length=63), table=<runs>))?

Which pod or UI is that error appearing in dusty?

This log/stack trace is from the dagster-run k8s pod that gets started at the beginning of the DAG run (it throws that error but stays in a

running

state)

Hmmm any chance you could share the Dockerfile for that image? That would be an image that you provide right?

Yea, and it’s built using poetry for dependency management. On 1.1.13, i was able to fix it by pinning sqlalchemy to 1.4.46

Very strange - I’m pretty confident the sqlalchemy pin is correct in 1.1.14, not sure why poetry wouldn’t respect that

Let me start over. I’ll remove SQLALchemy from the poetry toml, make sure my other dependancies are updated and go from there (keeping Dagster Helm Chart at 1.1.14, as well)

No worries!