https://dagster.io/ logo
Title
s

Seth Kimmel

06/01/2022, 5:10 PM
Is there a place to quickly see what version of Python cloud is running? Looking at the GUI and https://github.com/dagster-io/dagster-cloud release history.
d

daniel

06/01/2022, 5:13 PM
Hey Seth - your Dagster code can run in whichever version of Python you want, depending on the base image that you choose, as can your agent. I believe that the default Dagster Cloud agent image that we provide uses Python 3.8
Or do you mean like the hosted Dagit backend server?
s

Seth Kimmel

06/01/2022, 5:15 PM
Hmm whichever tells me the version of Python being used to interpret my code running in cloud
d

daniel

06/01/2022, 5:16 PM
Got it - that would depend on how you're building your code, since it's your agent that interprets the Python code using an image that you provide
s

Seth Kimmel

06/01/2022, 5:17 PM
We're running on ECS and I believe launched the agent stack from this page: https://docs.dagster.cloud/agents/ecs/setup.
d

daniel

06/01/2022, 5:18 PM
What are you using for CI/CD? That'll be what determines the base image for your code
s

Seth Kimmel

06/01/2022, 5:18 PM
Using GH actions
d

daniel

06/01/2022, 5:19 PM
Got it - so in the locations.yaml for our github action, there's a 'base_image' field: https://github.com/dagster-io/dagster-cloud-cicd-action-quickstart/blob/main/locations.yaml#L10
If you're using that action, that'll be what determines your python version
s

Seth Kimmel

06/01/2022, 5:19 PM
ah there it is
thanks so much again @daniel!
:condagster: 1
@daniel while I have you, this message just appeared when I merged some new code into main and triggered the stack update (via GH action). It may self-correct but figured I should flag
Looks like it is self-correcting, so probably no action req'd
d

daniel

06/01/2022, 5:38 PM
hm, ok - there's a timeout param that you can increase in the task definition that will make it wait longer before giving up
s

Seth Kimmel

06/01/2022, 5:39 PM
Well actually it's erroring again
Where is the timeout param?
d

daniel

06/01/2022, 5:40 PM
the timeout will only help if the task does eventually start up - if you look at the logs for the task in the ECS console that's referenced there, does it look like its starting up correctly?
s

Seth Kimmel

06/01/2022, 5:40 PM
And should I just hit Redeploy to let it try again?
d

daniel

06/01/2022, 5:41 PM
Yeah, Redeploy will make it try again
s

Seth Kimmel

06/01/2022, 5:45 PM
Failed again. Looks like a dependency issue
d

daniel

06/01/2022, 5:46 PM
Ah yes, protobuf released a backwards incompatible version. Options are either to upgrade dagster, or pin protobuf to <4
s

Seth Kimmel

06/01/2022, 5:47 PM
Will dagster 0.14.7 work?
We're running 0.14.5
d

daniel

06/01/2022, 5:55 PM
Yeah, latest dagster version (and dagster-cloud version) should resolve it
:next-level-daggy: 1
s

Seth Kimmel

06/01/2022, 5:58 PM
fixed!
😛artydagster: 1
Do ya'll mind being a bit more vocal in #dagster-cloud when there are breaking changes like this? Not a big deal this time but could be in the future
Maybe it was vocalized elsewhere and I didn't catch it?
d

daniel

06/01/2022, 6:02 PM
Yeah, that's a good callout. We'll stick an FYI in the future when an upstream library breaks
❤️ 1