Package update gets stalled for some reason

Nothing seems to happen when I run up, and on aborting the process with CTRL+C, this is what I find:

(@v1.9) pkg> up
^C^Cfatal: error thrown and no exception handler available.
InterruptException()
_jl_mutex_unlock at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/threading.c:795
jl_mutex_unlock at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/julia_locks.h:81 [inlined]
ijl_task_get_next at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/partr.c:394
poptask at ./task.jl:974
wait at ./task.jl:983
task_done_hook at ./task.jl:672
jfptr_task_done_hook_28284.clone_1 at /home/jishnu/packages/julias/julia-1.9/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2940
jl_apply at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/julia.h:1879 [inlined]
jl_finish_task at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/task.c:320
start_task at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/task.c:1103
β”Œ Warning: temp cleanup
β”‚   exception =
β”‚    schedule: Task not runnable
β”‚    Stacktrace:
β”‚      [1] error(s::String)
β”‚        @ Base ./error.jl:35
β”‚      [2] enq_work(t::Task)
β”‚        @ Base ./task.jl:769
β”‚      [3] yield
β”‚        @ ./task.jl:882 [inlined]
β”‚      [4] yield
β”‚        @ ./task.jl:880 [inlined]
β”‚      [5] Channel{Tuple{String, Vector{String}, Vector{String}}}(func::Base.Filesystem.var"#28#31"{String}, size::Int64; taskref::Nothing, spawn::Bool)
β”‚        @ Base ./channels.jl:140
β”‚      [6] Channel (repeats 2 times)
β”‚        @ ./channels.jl:132 [inlined]
β”‚      [7] #walkdir#27
β”‚        @ ./file.jl:967 [inlined]
β”‚      [8] walkdir
β”‚        @ ./file.jl:928 [inlined]
β”‚      [9] prepare_for_deletion(path::String)
β”‚        @ Base.Filesystem ./file.jl:507
β”‚     [10] temp_cleanup_purge(; force::Bool)
β”‚        @ Base.Filesystem ./file.jl:542
β”‚     [11] temp_cleanup_purge
β”‚        @ ./file.jl:535 [inlined]
β”‚     [12] (::Base.var"#930#931")()
β”‚        @ Base ./initdefs.jl:354
β”‚     [13] _atexit(exitcode::Int32)
β”‚        @ Base ./initdefs.jl:387
β”” @ Base.Filesystem file.jl:547
schedule: Task not runnable
atexit hook threw an error: ErrorException("schedule: Task not runnable")
error at ./error.jl:35
#schedule#649 at ./task.jl:840
schedule at ./task.jl:838 [inlined]
uv_writecb_task at ./stream.jl:1166
jfptr_uv_writecb_task_27933.clone_1 at /home/jishnu/packages/julias/julia-1.9/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2940
jlcapi_uv_writecb_task_40003.clone_1 at /home/jishnu/packages/julias/julia-1.9/lib/julia/sys.so (unknown line)
uv__write_callbacks at /workspace/srcdir/libuv/src/unix/stream.c:959
uv__stream_io at /workspace/srcdir/libuv/src/unix/stream.c:1294
uv__run_pending at /workspace/srcdir/libuv/src/unix/core.c:804
uv_run at /workspace/srcdir/libuv/src/unix/core.c:392
ijl_task_get_next at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/partr.c:390
poptask at ./task.jl:974
wait at ./task.jl:983
uv_write at ./stream.jl:1048
unsafe_write at ./stream.jl:1120
write at ./strings/io.jl:244 [inlined]
print at ./strings/io.jl:246
jfptr_print_52023.clone_1 at /home/jishnu/packages/julias/julia-1.9/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2940
showerror at ./errorshow.jl:144
unknown function (ip: 0x7f951d91b156)
_jl_invoke at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2940
_atexit at ./initdefs.jl:390
jfptr__atexit_44335.clone_1 at /home/jishnu/packages/julias/julia-1.9/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/gf.c:2940
jl_apply at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/julia.h:1879 [inlined]
ijl_atexit_hook at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/init.c:280
ijl_exit at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/init.c:207
ijl_no_exc_handler at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/task.c:712
jl_finish_task at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/task.c:323
start_task at /cache/build/default-amdci4-6/julialang/julia-release-1-dot-9/src/task.c:1103

I had also seen this message once:

attempting to remove probably stale pidfile

but the update seemingly was stalled after this.

After removing the ~/.julia directory, I find

(@v1.9) pkg> up
  Installing known registries into `~/.julia`
β”Œ Warning: could not download https://pkg.julialang.org/registries
β”‚   exception = RequestError: HTTP/2 301 (Connection timeout after 30029 ms) while requesting https://pkg.julialang.org/registries
β”” @ Pkg.Registry ~/packages/julias/julia-1.9/share/julia/stdlib/v1.9/Pkg/src/Registry/Registry.jl:69

Is there an issue with the registries? Or is this something at my end?

I’m also having the same problem. I think https://pkg.julialang.org/ is down at the moment.

2 Likes

Looking at https://status.julialang.org/, it seems that in.pkg.julialang.org is the one that’s down, while the others are up.

I can also load e.g. https://us-west.pkg.julialang.org/ in a browser, and a current workaround seems to be to set

julia> ENV["JULIA_PKG_SERVER"] = "us-west.pkg.julialang.org"
"us-west.pkg.julialang.org"

before attempting the upgrade (or set it to any of the other working servers, depending on one’s location).

2 Likes