REPLExt error with Julia 1.11.8

[mchitre]

After upgrading to Julia 1.11.8, I am seeing this:

(@v1.11) pkg> Unhandled Task ERROR: KeyError: key Base.PkgId(Base.UUID("e5eb5ef1-03cf-53a7-ae1d-5a66b08e832b"), "REPLExt") not found
Stacktrace:
 [1] pop!
   @ ./dict.jl:583 [inlined]
 [2] end_loading
   @ ./loading.jl:2140 [inlined]
 [3] macro expansion
   @ ./loading.jl:2724 [inlined]
 [4] macro expansion
   @ ./lock.jl:273 [inlined]
 [5] require_stdlib(package_uuidkey::Base.PkgId, ext::String, from::Module)
   @ Base ./loading.jl:2689
 [6] load_pkg()
   @ REPL ~/.julia/juliaup/julia-1.11.8+0.aarch64.apple.darwin14/share/julia/stdlib/v1.11/REPL/src/Pkg_beforeload.jl:8
 [7] (::REPL.var"#123#141"{REPL.LineEdit.MIState, REPL.LineEditREPL, REPL.LineEdit.Prompt})()
   @ REPL ~/.julia/juliaup/julia-1.11.8+0.aarch64.apple.darwin14/share/julia/stdlib/v1.11/REPL/src/REPL.jl:1284

if I do a using Revise in my startup.jl. If I comment that out, everything is good.

If I manually load Revise after starting the REPL, everything is good. If I change Julia version to 1.12.3, everything is good.

[IanButterworth]

Can you rename your v1.11 manifest and try again. (rename not delete, so we can investigate if it fixes it)

[mchitre]

Still the same after removing Manifest.toml and re-instantiating my environment.

[IanButterworth]

Thanks.

So #58415 was backported to 1.11.8 and that had previously caused the same issue, and the fix wasn't backported from what I can tell.

[IanButterworth]

I think my read is wrong (the commit history is squash merged so it's a bit confusing)

Apparently this should be fixed in 1.11.8 timholy/Revise.jl#905 (comment)

@DilumAluthge

[IanButterworth]

Just adding that @mchitre reported to not be setting JULIA_DEPOT_PATH to anything custom, so it's not that the bundled pkgimages are being excluded.

[DilumAluthge]

I'm able to reproduce this on Julia 1.11.8 and on the tip of release-1.8.

I can also confirm that checking out release-1.8 and reverting bef4090 fixes the bug.

@vtjnash Any idea why bef4090 would introduce this bug? And if there is a way to fix it?

---

We are also faced with a second problem: Julia 1.11 is no longer supported. Normally, we wouldn't have even released 1.11.8, but we did it as kind of a special case. The problem is that I kind of promised everyone that 1.11.8 would be the last 1.11 release. So I'm not sure if I can get buy-in for making another 1.11 release (even if we can find a fix for the bug).

[KristofferC]

The problem is that I kind of promised everyone that 1.11.8 would be the last 1.11 release. So I'm not sure if I can get buy-in for making another 1.11 release (even if we can find a fix for the bug).

I don't see any harm in another 1.11 release. I don't think the incremental work is that high.