Precompilation problem on 1.11 with complete_remote_package about pluto.jl

[j-fu]

Yes, this indeed seems like a hack.
Did some research: in 1.10, complete_remote_package is in the REPLMode submodule, and not exported. Formally, then it is not part of the public API.

Not sure if it make sense to code a work-around in Pluto now.

IMHO in 1.11 this could be made part of public API using the new public keyword. According to the logic of extensions, once it is public, Pkg.jl somwehre needs to declare

public function complete_remote_package end

Then the extension would extend this function once REPL is loaded.
IMHO this would warrant an issue or a PR with Pkg.jl .

[balenamiaa]

I think this is because complete_remote_package is defined in an package extension of REPL now. It's used in _registered_package_completions. Replacing Pkg.REPLMode with REPLExt where

using REPL
const REPLExt = Base.get_extension(Pkg, :REPLExt)

fixes it for me, but this seems like a hack.

[j-fu]

const REPLExt = Base.get_extension(Pkg, :REPLExt)

Well, I just tried this out, the error as described in the gist persists.
The error occurs when calling RegistryInstances.reachable_registries() during precompilation:

Pluto.jl/src/packages/PkgCompat.jl

Line 170 in 9f9ab2e

_get_registries() = RegistryInstances.reachable_registries()

I can call RegistryInstances.reachable_registries() from the REPL without problems. So there seems to be more to the picture, and we have at least two problems:

• fix the situation with complete_remote_package
• figure out what is going on with RegistryInstances.reachable_registries()