-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
External Pkg always recompiles upon loading #54940
Comments
What does |
weird.. |
I am also surprised this doesn't print anything at all for Base64:
|
I had some thought that the nightly build juliaup uses was corrupt somehow but building a local Julia on master it gives the exact same behavior. |
Base64 is an indirect dep of REPL, so it's already loaded? |
This method of loading Pkg seems to work:
|
Okay, that makes sense, I looked in
so I guess things that are loaded as part of But that shouldn't make Pkg have to compile over and over due to error when reading the Base64 pkgimage file I guess. |
I have seen this too when trying to debug JuliaPy/PythonCall.jl#513. |
I ran a git bisect for the function I needed not being exported, and it
fingered this commit. Maybe multiple things are wrong?
…On Wed, Jun 26, 2024 at 9:26 AM Kristoffer Carlsson < ***@***.***> wrote:
There @kshyatt <https://github.com/kshyatt> nailed down the problem to
71fa11f
<71fa11f>
.
Same thing happens when I revert that commit.
—
Reply to this email directly, view it on GitHub
<#54940 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGKJY5FPJRFDYJSRJHFI4TZJK6P5AVCNFSM6AAAAABJ5V7TROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJRGY4TSNJQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, I think they are unrelated. |
Same happens with OhMyREPL on nightly:
|
More followup to fix issues with require. There was an accidental variable reuse (build_id) that caused it to be unable to load cache files in many cases. There was also missing check for a dependency already being loaded, resulting in trying to load it twice. Finally, the start_loading code may drop the require_lock, but the surrounding code was not prepared for that. Now integrate the necessary checks into start_loading, instead of needing to duplicate them before and afterwards. Fixes #53983 Fixes #54940 Closes #55064
More followup to fix issues with require. There was an accidental variable reuse (build_id) that caused it to be unable to load cache files in many cases. There was also missing check for a dependency already being loaded, resulting in trying to load it twice. Finally, the start_loading code may drop the require_lock, but the surrounding code was not prepared for that. Now integrate the necessary checks into start_loading, instead of needing to duplicate them before and afterwards. Fixes #53983 Fixes #54940 Closes #55064
More followup to fix issues with require. There was an accidental variable reuse (build_id) that caused it to be unable to load cache files in many cases. There was also missing check for a dependency already being loaded, resulting in trying to load it twice. Finally, the start_loading code may drop the require_lock, but the surrounding code was not prepared for that. Now integrate the necessary checks into start_loading, instead of needing to duplicate them before and afterwards. Fixes #53983 Fixes #54940 Closes #55064
More followup to fix issues with require. There was an accidental variable reuse (build_id) that caused it to be unable to load cache files in many cases. There was also missing check for a dependency already being loaded, resulting in trying to load it twice. Finally, the start_loading code may drop the require_lock, but the surrounding code was not prepared for that. Now integrate the necessary checks into start_loading, instead of needing to duplicate them before and afterwards. Fixes #53983 Fixes #54940 Closes #55064 (cherry picked from commit fba928d)
While being in a Pkg.jl repo:
The two original misses are from the bundled cache files so those are expected. This is also a bit weird:
The text was updated successfully, but these errors were encountered: