-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Starlette Issue with Dagster 1.6.1 & Starlette 0.36.0 #19356
Comments
I'm experiencing the same issue as @cody-scott. I was able to work around it by pinning to an older version of starlette in the Dockerfile that builds my dagster-webserver image. |
I believe this is an issue in the |
Agreed. Since dagster isn't pinning the version I imagine it'll be popping up for others no? |
I hit that bug 2h after starlette 0.36.0 was released yesterday. Fixed it by pinning the version of |
encode/starlette#2436 `0.36.1` fixed it resolves #19356 ## How I Tested These Changes bk
Dagster version
1.6.1
What's the issue?
When launching the dev environment with dagster version locked at 1.6.1, starlette is updating to 0.36.0 and fails to launch with the following error:
resolved by locking "starlette<0.36.0"
What did you expect to happen?
Dagster UI to launch on localhost:3000.
Problem also happened on earlier version (1.5.12).
How to reproduce?
setup.py file
Deployment type
Docker Compose
Deployment details
development is in a devcontainer.
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: