-
-
Notifications
You must be signed in to change notification settings - Fork 321
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
Default installation of JAX + Tensorflow produces inconsistent environment #437
Comments
I can recreate. Thank you for the detailed information. I think that:
If you could:
that would help alleviate things |
I believe this should be resolved now, no? At least the current packages are compatible. A repodata patch may be worthy tho |
If I add If I don't do this then the default base image, |
Okay, I see. Btw, is this for a GPU or CPU deployment? I highly recommend you follow hmaarrfk's recommendation above. Our jaxlib>=0.3.10 (thus jax>=0.3.10) and tensorflow>=2.8.1 are somewhat different from previous versions (enabling XLA for tf and adding cuda for jax). Also, both are slightly more advanced in terms of migrations (they're incompatible with things like gdal, etc. as the latter haven't been migrated to the latest icu). |
I've only tested on CPU. I was indeed able to work around things with @hmaarrfk's suggestions above, so thanks for that! |
Who is in charge of condaforge/miniforge3:latest? We can just bump that up? Re CPU vs GPU, I am asking because our current recommendation is that users specify |
Solution to issue cannot be found in the documentation.
Issue
Installing default versions of both JAX and Tensorflow from conda-forge currently results in an inconsistent environment in which neither of them can be imported. Using either of the two separately is fine.
I can recreate this in the miniforge3 docker image like this
which gives the following error:
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: