mkitti
December 4, 2023, 11:59pm
21
Tetrakai:
After seeing the results in my last post do you think I should still open the github issue with Lux?
It seems to me this specific problem could be fixed but ultimately it is with how the package manager handles dependencies with extensions (correct me if Iβm wrong, I just started trying Julia last month). As you say, depending on order of installation is descending into a whole new lower level of dependency hell.
The output suggests there are some problems with extension packages. I have not figured out if it is specific to a couple extension packages or if there is a particular issue with how extension packages are activated and compiled in general.
Extension packages are relatively new and are loaded when two or more packages are loaded. Perhaps @kristoffer.carlsson can interpret your pastebin better than I as well.
module ComponentArraysAdaptExt
using ComponentArrays, Adapt
function Adapt.adapt_structure(to, x::ComponentArray)
data = Adapt.adapt_structure(to, getdata(x))
return ComponentArray(data, getaxes(x))
end
Adapt.adapt_storage(::Type{ComponentArray{T,N,A,Ax}}, xs::AT) where {T,N,A,Ax,AT<:AbstractArray} =
Adapt.adapt_storage(A, xs)
end
Iβm going to ping @avikpal since he authored many of the extension packages in question.
This should not be an issue. juliaup development is pretty tightly coordinated with Julia. Itβs an official mechanism of installing Julia. It also stores content in ~/.julia by default.
3 Likes
jishnub
December 5, 2023, 9:07am
22
I could not reproduce it yet, unfortunately. It took several minutes but it compiled everything nicely and using... works too:
Full REPL output
β tamasgal@silentbox-(6):tmp/precompile ξ main Β»β( )_ | Documentation: https://docs.julialang.org ) | ( ) () || | __ _ | Type β?β for help, β]?β for Pkg help.` | | | | | | ( | | | Version 1.9.4 (2023-11-14)/ |_ β| ||_ β_| | Official https://julialang.org/ release
(precompile) pkg> add ComponentArrays@v0.15.5~/.julia/registries/KM3NeTgit@git.km3net.de:common/julia-registry.git~/.julia/registries/General.toml~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.toml~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.toml~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.tomlstatus --outdated -m~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.toml~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.toml~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.toml~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.tomlstatus --outdated -m~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.toml~/tmp/precompile/Project.toml~/tmp/precompile/Manifest.toml
julia> using Lux, ComponentArrays, SciMLSensitivity, LuxAMDGPU, LuxCUDA,
julia>
Did you ensure the packages werenβt already present in ~/.julia/packages?
That was a key step that doesnβt seem to show up in the REPL logs. For my last pastebin I know the packages were downloaded fresh from the registry because I was watching them get added. However, there is no mention of βdownloadingβ all of them in the logs.