-
Notifications
You must be signed in to change notification settings - Fork 81
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
ModuleNotFoundError: No module named 'jax.experimental.maps' after main-brunch update (#662) #673
Comments
yeah looks like they moved/removed jax.experimental.maps. the container sticks close to JAX head, which we don't. |
Once I merge stanford-crfm/haliax#102 and a suitable interval for the package to propagate, you should be able to update to the latest dev version of haliax (probably 308 or 309) |
try |
This comment was marked as outdated.
This comment was marked as outdated.
Please ignore and let me retest - I wasn't on Levanter head so that might be it. Will follow up |
Yeah same output unfortunately. Is there a way I can access older jax containers?
|
this seems like a probelm with the cuda stuff. @DwarKapex Any thoughts? |
(You can probably use https://github.com/orgs/nvidia/packages/container/jax/248105500?tag=levanter-2024-07-24 as jax:levanter-2024-07-24) |
that did the trick! Thanks so much! |
If it is of any help to you here is a slightly more detailed description of what I am trying to do.
Sharing this in case it helps you guys with debugging. Feel free to follow up if you have any question. |
weird. that's easy to workaround but I don't know why it's happening |
Hi - after yesterday's code update I am getting the following error. Any advise? I am using the Jax-levanter docker image
EDIT: Actually I now see the main error with previous repo HEAD, which is weird cause yesterday the container was working fine. You think something has change on the NVIDA-image ?
The text was updated successfully, but these errors were encountered: