-
Notifications
You must be signed in to change notification settings - Fork 79
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
Cannot use --nvidia flag with updated empy==4.0 #259
Comments
I have a fix in #260 if I can't find a full fix for compatibility, I'll merge that pinback short term and keep this open. |
Working towards #259 This is not backwards compatible at the moment. But works with empy==4.0
Can you try out the fix in #261 on your system? |
Thanks, that's fixed it 👍. I ran:
With that I am now able to run rocker with the nvidia flag: Pip freeze confirms I am in fact using empy 4:
|
Thanks for verifying the fix! |
Oh, follow up question - would you consider updating the pypi release version to current main? My CI is still failing because the current pypi release 0.2.12 does not include the empy fix. Not sure how much hassle it is for you to push a new release. |
Hi there, I've noticed from my CI that fresh rocker installs are failing to run rocker with the --nvidia flag.
I've traced this back to a new empy release overnight, from version 3.3.4 to 4.0:
https://pypi.org/project/empy/#history
I'm not sure if this is an empy bug, or a breaking API change requiring an update in rocker, in any case I'm logging a ticket here for awareness.
Here's how I reproduce the issue on Ubuntu 20.04.6 LTS, Python 3.8.10:
This produces output:
Package versions for the above error:
Rolling back empy to the previous version resolves the issue:
The text was updated successfully, but these errors were encountered: