-
Notifications
You must be signed in to change notification settings - Fork 206
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
Properly pin MPICH_jll #2488
Properly pin MPICH_jll #2488
Conversation
according to https://pkgdocs.julialang.org/v1/compatibility/, `MPICH_jll = "4.0.1"` means `[4.0.1 - 5.0.0)` and it's not what we want!
Thanks @navidcy |
approve? |
was on my phone 🥺 |
I'll merge when tests pass! |
cool, do that... and register a new version! |
I paused the release of 0.75.3 when I realised the pinning was not done correctly. |
wow, I didn't know you could do that |
I don't think we should pin a indirect dependency. Using Julia 1.7 with Mac M1 is decidedly unsupported and the user can do the pinning in their |
Ah, I didn't realize this was specifically a Mac M1 issue. I think we'll continue to get issues and questions about this error if we don't do something about it (and its very inconvenient for this important subset of users). What's the best way to solve this problem? |
There is a Mac M1 version of Julia at https://julialang.org/downloads/ so people will download that and try to use Oceananigans with it... |
Maybe @vchuravy's point is that it's labeled "experimental" so problems are expected. So we either live with inconvenience (experimental=inconvenience expected) or use temporary dirty solutions like this. I guess from "our perspective", 1.7 "basically works" except for this. So while it's experimental on M series in general, it seems we "want" to label it as supported via this PR. Maybe we shouldn't. |
I agree ghat is not optimal to pin an indirect dep (which we made direct now). But if that solves issue for some users let’s do it. |
Any code using threading is eventually just going to hang on M1. My point is that Oceanigans should not be working around this for the user since it declares an unecessary dependency for everyone else. Users can pin mpich_jll locally if needed. |
Interesting. I didn't know that! |
In particular JuliaLang/julia#41820 |
OK. How about we close this PR and open another on in which we:
|
Closing this in favor of #2496 |
According to https://pkgdocs.julialang.org/v1/compatibility/,
MPICH_jll = "4.0.1"
means[4.0.1 - 5.0.0)
and it's not what we wanted!(And indeed, when I called
using Pkg; Pkg.update()
MPICH_jll got updated to 4.0.2.)