-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' #21920
Comments
Having the same issue after update to 1.7.6 version (python 3.11) |
Hi, thanks for reporting this - we're working on a fix and it looks like this was indeed introduced in 1.7.6. Is it possible to confirm whether or not this error is preventing the run from completing? |
@gibsondan jobs and schedules work as usual, runs complete correctly. It seems like it mostly affects execution of watch_orphans.py utility. |
Got it - thanks for confirming. Our current plan is to include a fix for this in the release planned for next week since the main impact appears to be logspew and the error doesn't fail runs or prevent logs from runs from being submitted (the utility process in question does some cleanup of orphaned subprocesses if the process running a step happens to crash mid-execution). Downgrading to 1.7.5 should also prevent the error from being logged in the interim. |
…d shadowing dependencies relates to #21920
## Summary & Motivation #21920 ## How I Tested These Changes - BK
## Summary & Motivation Relates to #21920 ## How I Tested These Changes Tested with ./examples/deploy_docker/from_source/build.sh docker-compose set + launching a run to verify the problem is addressed
## Summary & Motivation #21920 ## How I Tested These Changes - BK
## Summary & Motivation Relates to #21920 ## How I Tested These Changes Tested with ./examples/deploy_docker/from_source/build.sh docker-compose set + launching a run to verify the problem is addressed
## Summary & Motivation dagster-io#21920 ## How I Tested These Changes - BK
## Summary & Motivation Relates to dagster-io#21920 ## How I Tested These Changes Tested with ./examples/deploy_docker/from_source/build.sh docker-compose set + launching a run to verify the problem is addressed
Dagster version
latest
What's the issue?
getting this exceptionOriginal, exception was:
What did you expect to happen?
getting error
How to reproduce?
while do etl it happened
Deployment type
Local
Deployment details
local
Additional information
nothing
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: