-
-
Notifications
You must be signed in to change notification settings - Fork 10
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 Tyler in Julia 1.11.2 #122
Comments
I actually also shortly got this in a project completely unrelated to Tyler... Really weird with the platform mismatch (it was on windows, so pretty far from risc-v). For me it went away after restarting Julia😅 |
I did that, also deleted compiled folder, and still same issue. So, no Tyler for me at the moment 😄 . |
https://github.com/JuliaBinaryWrappers/OpenSSL_jll.jl/releases/tag/OpenSSL-v3.0.15%2B2 There's a new release, the timing seems to fit.. maybe you can manually add the previous version. |
If you don't have |
don't think so (1.7.0 is the one being used):
|
The stacktrace doesn't make sense to me then: at https://github.com/JuliaPackaging/JLLWrappers.jl/blob/ecaba50a4462209714f0979667c64c1bf28ee892/src/toplevel_generators.jl#L115 we call |
Do you have stacked environments, with different versions of JLLWrappers in them? |
No, and if I do new env and then
|
I keep that you aren't using [email protected], the stacktrace doesn't match:
Line 113 in v1.7.0 is a comment, while in v1.6.1 it's the
|
Also,
I don't know how to better explain and prove that somehow you're using a different version of |
well... my global env only has Now, I just installed Julia again (deleted all 😄, was no patience enough to see where things were going wrong), and no issues now. Thanks for taking a look. |
You need to check
|
ohh gosh, so dumb (my first issue with this stacked environment logic).... yes... I didn't updated the manifest of |
Trying to use Tyler on Metal with Julia 1.11.2 fails, not sure if this is Julia version issue or OS error or a combo.
The text was updated successfully, but these errors were encountered: