Open aj-fleming opened 4 months ago
After a brief investigation, I found that Pluto chooses to set [compat]
entries to use a ~
, which explains the incorrect behavior.
However, removing the [compat]
section or changing the compat entry to something else failed to force an update. Removing the using
statement, re-running the notebook, restarting Pluto, adding the using
statement again, and then finally running the notebook also fails to update the package to the correct version.
Output from the Terminal after removing using Euler2D
from the first cell:
Updating `/tmp/jl_bLbYA9/Project.toml`
[c24a2923] - Euler2D v0.1.2
Updating `/tmp/jl_bLbYA9/Manifest.toml`
[79e6a3ab] - Adapt v4.0.4
[4fba245c] - ArrayInterface v7.11.0
[62783981] - BitTwiddlingConvenienceFunctions v0.1.5
[2a0fbf3d] - CPUSummary v0.2.5
[fb6a15b2] - CloseOpenIntervals v0.1.12
[adafc99b] - CpuId v0.3.1
[c24a2923] - Euler2D v0.1.2
[3e5b6fbb] - HostCPUFeatures v0.1.16
[615f187c] - IfElse v0.1.1
[10f19ff3] - LayoutPointers v0.1.15
[bdcacae8] - LoopVectorization v0.12.170
[d125e4d3] - ManualMemory v0.1.8
[6fe1bfb0] - OffsetArrays v1.14.0
[1d0040c9] - PolyesterWeave v0.2.1
[94e857df] - SIMDTypes v0.1.0
[476501e8] - SLEEFPirates v0.6.42
[aedffcd0] - Static v0.8.10
[0d7ed370] - StaticArrayInterface v1.5.0
[8290d209] - ThreadingUtilities v0.5.2
[3a884ed6] - UnPack v1.0.2
[3d5dd08c] - VectorizationBase v0.21.68
[4607b0f0] - SuiteSparse
Output from the "Package management" step in the status window, after restarting Pluto:
Resolving...
No Changes to `/tmp/jl_CHPHPj/Project.toml`
No Changes to `/tmp/jl_CHPHPj/Manifest.toml`
Adding packages...
Resolving package versions...
Updating `/tmp/jl_CHPHPj/Project.toml`
⌃ [c24a2923] + Euler2D v0.1.2
Updating `/tmp/jl_CHPHPj/Manifest.toml`
[79e6a3ab] + Adapt v4.0.4
[4fba245c] + ArrayInterface v7.11.0
[62783981] + BitTwiddlingConvenienceFunctions v0.1.5
[2a0fbf3d] + CPUSummary v0.2.5
[fb6a15b2] + CloseOpenIntervals v0.1.12
[adafc99b] + CpuId v0.3.1
⌃ [c24a2923] + Euler2D v0.1.2
[3e5b6fbb] + HostCPUFeatures v0.1.16
[615f187c] + IfElse v0.1.1
[10f19ff3] + LayoutPointers v0.1.15
[bdcacae8] + LoopVectorization v0.12.170
[d125e4d3] + ManualMemory v0.1.8
[6fe1bfb0] + OffsetArrays v1.14.0
[1d0040c9] + PolyesterWeave v0.2.1
[94e857df] + SIMDTypes v0.1.0
[476501e8] + SLEEFPirates v0.6.42
[aedffcd0] + Static v0.8.10
[0d7ed370] + StaticArrayInterface v1.5.0
[8290d209] + ThreadingUtilities v0.5.2
[3a884ed6] + UnPack v1.0.2
[3d5dd08c] + VectorizationBase v0.21.68
[4607b0f0] + SuiteSparse
Info Packages marked with ⌃ have new versions available and may be upgradable.
Loading packages...
Instantiating...
Precompiling...
Activating project at `/tmp/jl_CHPHPj`
Output from Pkg
in a fresh julia project folder:
activate .
Activating new project at `~/projects/pkgjltest`
(pkgjltest) pkg> add Euler2D
Resolving package versions...
Updating git-repo `git@github.com:STCE-at-RWTH/Euler2D.jl.git`
Installed Euler2D ─ v0.2.1
Updating `~/projects/pkgjltest/Project.toml`
[c24a2923] + Euler2D v0.2.1
Updating `~/projects/pkgjltest/Manifest.toml`
[d360d2e6] + ChainRulesCore v1.24.0
[34da2185] + Compat v4.15.0
[b552c78f] + DiffRules v1.15.1
[ffbed154] + DocStringExtensions v0.9.3
[c24a2923] + Euler2D v0.2.1
[92d709cd] + IrrationalConstants v0.2.2
[692b3bcd] + JLLWrappers v1.5.0
[2ab3a3ac] + LogExpFunctions v0.3.28
[77ba4419] + NaNMath v1.0.2
[21216c6a] + Preferences v1.4.3
[ae029012] + Requires v1.3.0
[77d2bf28] + ShockwaveProperties v0.1.11
[276daf66] + SpecialFunctions v2.4.0
[bc48ee85] + Tullio v0.3.7
[1986cc42] + Unitful v1.20.0
[f31437dd] + UnitfulChainRules v0.1.2
[efe28fd5] + OpenSpecFun_jll v0.5.5+0
[0dad84c5] + ArgTools v1.1.1
[56f22d72] + Artifacts
[2a0f44e3] + Base64
[ade2ca70] + Dates
[f43a241f] + Downloads v1.6.0
[7b1f6079] + FileWatching
[b77e0a4c] + InteractiveUtils
[b27032c2] + LibCURL v0.6.4
[76f85450] + LibGit2
[8f399da3] + Libdl
[37e2e46d] + LinearAlgebra
[56ddb016] + Logging
[d6f4376e] + Markdown
[ca575930] + NetworkOptions v1.2.0
[44cfe95a] + Pkg v1.10.0
[de0858da] + Printf
[3fa0cd96] + REPL
[9a3f8284] + Random
[ea8e919c] + SHA v0.7.0
[9e88b42a] + Serialization
[6462fe0b] + Sockets
[fa267f1f] + TOML v1.0.3
[a4e569a6] + Tar v1.10.0
[cf7118a7] + UUIDs
[4ec0a83e] + Unicode
[e66e0078] + CompilerSupportLibraries_jll v1.1.1+0
[deac9b47] + LibCURL_jll v8.4.0+0
[e37daf67] + LibGit2_jll v1.6.4+0
[29816b5a] + LibSSH2_jll v1.11.0+1
[c8ffd9c3] + MbedTLS_jll v2.28.2+1
[14a3606d] + MozillaCACerts_jll v2023.1.10
[4536629a] + OpenBLAS_jll v0.3.23+4
[05823500] + OpenLibm_jll v0.8.1+2
[83775a58] + Zlib_jll v1.2.13+1
[8e850b90] + libblastrampoline_jll v5.8.0+1
[8e850ede] + nghttp2_jll v1.52.0+1
[3f19e933] + p7zip_jll v17.4.0+2
Precompiling project...
1 dependency successfully precompiled in 2 seconds. 23 already precompiled.
Removing all packages from the notebook, then re-adding them seems to work.
Hey! This is most likely caused by https://github.com/fonsp/Pluto.jl/pull/2902 . You should be able to get the latest version by clicking the "update" button after the package is installed.
The reasoning here is that most people care much more about fast launch times than getting the very latest versions. We get a lot of feedback about slow launches with recent Julia versions.
I had absolutely no idea I could click on that check mark. It makes sense that most people would prefer faster load times -- problem solved.
Thanks!
Did clicking the update button solve your problem? Maybe we should improve the GUI (because the text "vx.y.z will be installed" is wrong)? I only recently added this to our documentation:
https://plutojl.org/en/docs/packages/#pre-installed-versions-are-preferred
Do you have suggestions for how this can be made more clear?
The update button did solve the problem.
Updating the mouseover text to show the correct version that will be installed, or perhaps "vX.Y.Z" is already installed on this system" would make it more clear what's going on.
Adding a visual cue to the check mark after using
statements to indicate that it can be clicked would also be a great improvement.
More confusion in https://github.com/fonsp/Pluto.jl/issues/2947
Thanks. Just to clarify my comment in #2947, it doesn't work for me to press the update button. Pluto goes through the motions to update all packages, but doesn't update my package unless I remove the compat
restriction (either manually in the notebook file or though Pluto.activate_notebook_environment
and ] compat
).
Sorry, I know it's not helpful, I'll try to dig into this some on the weekend maybe.
If I want to load a package that has been recently updated, Pluto often loads a less-recent version of the package.
The mouseover before running the notebook displays "Euler2D (v0.2.1) will be installed while running this notebook" on mouseover, but the version that's actually installed is a previous version (v0.1.2).
I'm not sure how to demonstrate this, but I'm able to reliably reproduce the issue by updating a package that I develop, updating the registry the package is in (this also works with the General registry), and running a Pluto notebook that
use
s the newly updated package.