-
Notifications
You must be signed in to change notification settings - Fork 111
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
Warnings on Julia v1.10.1 when installing or loading packages #802
Comments
I'm seeing the same here. I'm willing to provide warning outputs or test any potential fixes if helpful. |
Same here |
I bisected this to JuliaLang/julia#52637, More reports on discourse https://discourse.julialang.org/t/revise-warnings-on-v1-10-1/110237/9 CC: @KristofferC |
This makes the julia process partially broken, because for example the fallback method for mean(::AbstractArray) is deleted and then I can't plot anymore with Makie. |
Thanks, I will try to understand what's going on. |
I cannot reproduce this locally so I will just revert that PR for 1.10.2. I don't see anything wrong with it though so perhaps this is a bug in Revise. |
Looks like it is finding the build path of julia, not sure why.
Looks like it thinks it would get the directory of the package somewhere but instead got the full path including |
I might understand from:
There is an inconsistency there that with the stdlib we get a path to the entry file while with the normal package we get the path to the folder. For Base itself this turns out to not matter but Revise uses some internals from code loading: Line 410 in dbbeb35
|
Can people try out #806? I'm having some troubles reproducing this myself so some help would be good. |
3.5.14 is on the way through the registration system. If someone can repro this with that Revise version please comment |
3.5.14 seems to work for me |
Seems to be resolved here too, thanks! |
I'm relatively reliably being able to replicate the following warnings on Julia v1.10.1:
These seem to persist even if I delete the compiled cache and the package directories, as well as the default environment manifest.
The text was updated successfully, but these errors were encountered: