-
-
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
[backports-release-1.11] Loading backports #56476
base: backports-release-1.11
Are you sure you want to change the base?
[backports-release-1.11] Loading backports #56476
Conversation
…ic structures (mostly eachindex) (JuliaLang#55137) Base should be a model for the ecosystem, and `eachindex(x)` is better than `1:length(x)` in almost all cases. I've updated many, but certainly not all examples. This is mostly a NFC, but also fixes JuliaLang#55136. (cherry picked from commit 0945b9d)
…ckages are in the sysimage (JuliaLang#52841)" This reverts commit 08d229f. (cherry picked from commit e3f2f6b)
(cherry picked from commit ad1dc39)
…ecompile loading (JuliaLang#56291) Fixes `_require_search_from_serialized` to first acquire all start_loading locks (using a deadlock-free batch-locking algorithm) before doing stalechecks and the rest, so that all the global computations happen behind the require_lock, then the rest can happen behind module-specific locks, then (as before) extensions can be loaded in parallel eventually after `require` returns. (cherry picked from commit db3d816)
Guarantee that `__init__` runs before `using` returns. Could be slightly breaking for people that do crazy things inside `__init__`, but just don't do that. Since extensions then probably load after `__init__` (or at least, run their `__init__` after), this is a partial step towards changing things so that extensions are guaranteed to load if using all of their triggers before the corresponding `using` returns Fixes JuliaLang#55556 (cherry picked from commit 9dbdeb4)
@nanosoldier |
Whoops, premature pkgeval.. needs JuliaLang/Pkg.jl#4078 |
Revise tests are hitting ConcurrencyViolationErrors
|
If we expect this to be a public API (https://github.com/timholy/Revise.jl for some reason is trying to access this state), we should lock around it for consistency with the other similar functions. Needed for timholy/Revise.jl#856 (cherry picked from commit 4cdd864)
That required #56027 which wasn't marked for backport. If we go with this PR, a few of these need the label added and removed, so it's clear they have been backported. |
REPL is detecting unexpected precompiles during startup on this branch that aren't on #56228
|
The package evaluation job you requested has completed - possible new issues were detected. |
This is as far as I got with backports to try and get #56329 in to fix #56077
#56329 stumped me.
@vtjnash would you mind helping here.