-
-
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
1.11 regression: REPL error if starting julia with -O3
#56054
Comments
-O3
-O3
Does the bug occur on Julia 1.10.5? |
Not for me, no. I've had the bash alias
for a very long time (maybe since 1.6 or 1.7?) and have never seen this issue before. |
-O3
-O3
On 1.11, what do other values for |
Ah, good idea! It is just |
I confirm precompiling but not error on 1.11.0 (and rc4), i.e. without -C"native"' but then an error with it see B. A.
[And this takes quite a long time, still running for me... After no progress for ca. 10 min I did CTRL-C.] I feel responsible, I got lowered opt in for the REPL, and suspect it related. If that's the case then there possibly needs to be a max. opt. option for packages (at least used by stdlibs). B.
|
This is somewhat expected that the REPL might need to compile a new copy (unable to use require_stdlib) with non-default options. Though I thought our intent is to compile everything at O3 with g2, so those at least don't cause recompilation (and currently seems those aren't getting propagated though) |
See: Line 17 in ecf41b1
[I see REPLExt in the code, that's it loaded, but not from where...] And this speed-optimization (for Pkg-related, actually for PythonCall indirectly) might be the cause (for the package mode): https://github.com/JuliaLang/Pkg.jl/pull/4015/files
What is g2? And is compiling with O3 just to avoid recompilation, then doing julia -O3? [When you lower opt. from I suppose never recompiled for slower, only when asking for higher than in (stdlib) packages, why I suggested a max opt option, for those packages that never need more opt.] |
If one uses a 1.10 manifest with 1.11 + -O3 things go bad:
|
Hm. That is interesting. A small clarification on my part though: I mention using
|
I just want to add that I'm seeing the same issue on Windows 11, with the following
|
when I do julia> using Pkg
(@v1.11) pkg> st
Status `C:\Users\prbzr\.julia\environments\v1.11\Project.toml` (empty project)
(@v1.11) pkg> Julia Version 1.11.0
Commit 501a4f25c2 (2024-10-07 11:40 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: 12 × Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
WORD_SIZE: 64
LLVM: libLLVM-16.0.6 (ORCJIT, skylake)
Threads: 12 default, 2 interactive, 7 GC (on 12 virtual cores) without it: (@v1.11) pkg> Unhandled Task ERROR: ArgumentError: Package REPLExt [e5eb5ef1-03cf-53a7-ae1d-5a66b08e832b] is required but does not seem to be installed:
- Run `Pkg.instantiate()` to install all recorded dependencies.
Stacktrace:
[1] _require(pkg::Base.PkgId, env::Nothing)
@ Base .\loading.jl:2423
[2] __require_prelocked(uuidkey::Base.PkgId, env::Nothing)
@ Base .\loading.jl:2300
[3] #invoke_in_world#3
@ .\essentials.jl:1088 [inlined]
[4] invoke_in_world
@ .\essentials.jl:1085 [inlined]
[5] _require_prelocked
@ .\loading.jl:2287 [inlined]
[6] _require_prelocked
@ .\loading.jl:2286 [inlined]
[7] macro expansion
@ .\loading.jl:2587 [inlined]
[8] macro expansion
@ .\lock.jl:273 [inlined]
[9] require_stdlib(package_uuidkey::Base.PkgId, ext::String)
@ Base .\loading.jl:2542
[10] macro expansion
@ C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\Pkg_beforeload.jl:8 [inlined]
[11] macro expansion
@ .\lock.jl:273 [inlined]
[12] load_pkg()
@ REPL C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\Pkg_beforeload.jl:7
[13] (::REPL.var"#119#137"{REPL.LineEdit.MIState, REPL.LineEditREPL, REPL.LineEdit.Prompt})()
@ REPL C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\REPL.jl:1233
┌ Error: Error in the keymap
│ exception =
│ ArgumentError: Package REPLExt [e5eb5ef1-03cf-53a7-ae1d-5a66b08e832b] is required but does not seem to be installed:
│ - Run `Pkg.instantiate()` to install all recorded dependencies.
│
│ Stacktrace:
│ [1] _require(pkg::Base.PkgId, env::Nothing)
│ @ Base .\loading.jl:2423
│ [2] __require_prelocked(uuidkey::Base.PkgId, env::Nothing)
│ @ Base .\loading.jl:2300
│ [3] #invoke_in_world#3
│ @ .\essentials.jl:1088 [inlined]
│ [4] invoke_in_world
│ @ .\essentials.jl:1085 [inlined]
│ [5] _require_prelocked
│ @ .\loading.jl:2287 [inlined]
│ [6] _require_prelocked
│ @ .\loading.jl:2286 [inlined]
│ [7] macro expansion
│ @ .\loading.jl:2587 [inlined]
│ [8] macro expansion
│ @ .\lock.jl:273 [inlined]
│ [9] require_stdlib(package_uuidkey::Base.PkgId, ext::String)
│ @ Base .\loading.jl:2542
│ [10] macro expansion
│ @ C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\Pkg_beforeload.jl:8 [inlined]
│ [11] macro expansion
│ @ .\lock.jl:273 [inlined]
│ [12] load_pkg()
│ @ REPL C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\Pkg_beforeload.jl:7
│ [13] (::REPL.var"#109#127"{REPL.LineEditREPL})(s::REPL.LineEdit.MIState)
│ @ REPL C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\REPL.jl:1138
│ [14] on_enter(s::REPL.LineEdit.MIState)
│ @ REPL.LineEdit C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\LineEdit.jl:2314
│ [15] (::REPL.LineEdit.var"#120#176")(::REPL.LineEdit.MIState, ::Any, ::Vararg{Any})
│ @ REPL.LineEdit C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\LineEdit.jl:2464
│ [16] #invokelatest#2
│ @ .\essentials.jl:1054 [inlined]
│ [17] invokelatest
│ @ .\essentials.jl:1051 [inlined]
│ [18] (::REPL.LineEdit.var"#30#31"{REPL.LineEdit.var"#120#176", String})(s::Any, p::Any)
│ @ REPL.LineEdit C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\LineEdit.jl:1705
│ [19] macro expansion
│ @ C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\LineEdit.jl:2855 [inlined]
│ [20] macro expansion
│ @ .\lock.jl:273 [inlined]
│ [21] (::REPL.LineEdit.var"#282#284"{REPL.Terminals.TTYTerminal, REPL.LineEdit.ModalInterface, REPL.LineEdit.MIState, ReentrantLock, REPL.LineEdit.Prompt})()
│ @ REPL.LineEdit C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\LineEdit.jl:2845
└ @ REPL.LineEdit C:\Users\prbzr\.julia\juliaup\julia-1.11.0+0.x64.w64.mingw32\share\julia\stdlib\v1.11\REPL\src\LineEdit.jl:2857
julia> |
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. Fixes #56207 Fixes #56054 Fixes #56206
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. Fixes #56207 Fixes #56054 Fixes #56206
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. Fixes #56207 Fixes #56054 Fixes #56206
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. The printing also failed to meaningfully represent the settings for the same reasons. Fixes #56207 Fixes #56054 Fixes #56206
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. The printing also failed to meaningfully represent the settings for the same reasons. Also fixes a concurrency bug in loading.jl tests that was failing. Fixes #56207 Fixes #56054 Fixes #56206
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. Fixes #56207 Fixes #56054 Fixes #56206 (cherry picked from commit 82b1506)
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. Fixes #56207 Fixes #56054 Fixes #56206
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. Fixes #56207 Fixes #56054 Fixes #56206 (cherry picked from commit 82b1506)
CacheFlags could get set, but were never propagated to the target process, so the result would be unusable. Additionally, the debug and optimization levels were not synchronized with the sysimg, causing a regression in pkgimage usability after moving out stdlibs. Fixes #56207 Fixes #56054 Fixes #56206 (cherry picked from commit 82b1506)
Hello,
This issue also has a little discussion at this discourse link.
After upgrading to v1.11, I have an issue where if I start a REPL with
-O3
I get an error when I press]
to enter Pkg mode:If I instantiate a REPL without the flag, it works fine:
I have recreated this issue on two machines with the following versioninfo:
and
It seems like several other commenters on the discourse thread are experiencing something similar.
Is there a simple fix to this, or is this the result of a mistake on my end? I installed the updated version with
juliaup
, if that is relevant.Thanks so much!
The text was updated successfully, but these errors were encountered: