Follow up to #60. Uses a newer version of github-token-helper which doesn't result in a failure when interactively adding package when a private registry is present:
(JuliaProject) pkg> add LibPQ
Updating registry at `~/.julia/registries/Private`
Updating git-repo `https://github.com/example/PrivateRegistry`
Specified GitHub token file does not exist: /run/secrets/github_token
ERROR: IOError: write: broken pipe (EPIPE)
Stacktrace:
[1] uv_write(s::Base.PipeEndpoint, p::Ptr{UInt8}, n::UInt64)
@ Base ./stream.jl:1010
[2] unsafe_write(s::Base.PipeEndpoint, p::Ptr{UInt8}, n::UInt64)
@ Base ./stream.jl:1064
[3] unsafe_write(io::Base.Process, p::Ptr{UInt8}, nb::UInt64)
@ Base ./io.jl:362
[4] write
@ ./strings/io.jl:244 [inlined]
...
With this change:
(JuliaProject) pkg> add LibPQ
Updating registry at `~/.julia/registries/Private`
Updating git-repo `https://github.com/example/PrivateRegistry`
Specified GitHub token(s) could not be found
Username for 'https://github.com':
The "Specified GitHub token(s) could not be found" warning is from the github-token-helper and should probably be dropped but it's fine to have for now.
Follow up to #60. Uses a newer version of
github-token-helper
which doesn't result in a failure when interactively adding package when a private registry is present:With this change:
The "Specified GitHub token(s) could not be found" warning is from the
github-token-helper
and should probably be dropped but it's fine to have for now.