Hi,
A warning (about world age) is fetched when I load my project since I switched to Julia 1.12.
My project uses Plotly.jl which is the only package in Project.toml being related to WebIO.jl.
WARNING: Detected access to binding `WebIO.webio_serve` in a world prior to its definition world.
Julia 1.12 has introduced more strict world age semantics for global bindings.
!!! This code may malfunction under Revise.
!!! This code will error in future versions of Julia.
Hint: Add an appropriate `invokelatest` around the access to this binding.
To make this warning an error, and hence obtain a stack trace, use `julia --depwarn=error`.
versioninfo ans Pkg status
julia> versioninfo()
Julia Version 1.12.4
Commit 01a2eadb047 (2026-01-06 16:56 UTC)
Build Info:
Official https://julialang.org release
Platform Info:
OS: Linux (x86_64-linux-gnu)
CPU: 16 × 13th Gen Intel(R) Core(TM) i5-13600H
WORD_SIZE: 64
LLVM: libLLVM-18.1.7 (ORCJIT, alderlake)
GC: Built with stock GC
Threads: 16 default, 1 interactive, 16 GC (on 16 virtual cores)
Environment:
DYLD_LIBRARY_PATH = /home/G36749/opt/xpressmp/lib:
LD_LIBRARY_PATH = /home/G36749/opt/xpressmp/lib:
JULIA_EDITOR = code
JULIA_VSCODE_REPL = 1
JULIA_NUM_THREADS = 16
(Viviane) pkg> status
Project Viviane v0.1.0
Status `~/Projects/Julia/viviane.jl/Project.toml`
[ae650224] ChunkSplitters v3.1.2
⌅ [864edb3b] DataStructures v0.18.22
[5789e2e9] FileIO v1.17.1
[87dc4568] HiGHS v1.20.1
[5903a43b] Infiltrator v1.9.7
[c3a54625] JET v0.11.3
⌅ [033835bb] JLD2 v0.5.15
[0f8b85d8] JSON3 v1.14.3
[4076af6c] JuMP v1.29.3
[b8f27783] MathOptInterface v1.48.0
[c020b1a1] NaturalSort v1.0.0
[67456a42] OhMyThreads v0.8.4
[f0f68f2c] PlotlyJS v0.18.17
[f27b6e38] Polynomials v4.1.0
⌅ [08abe8d2] PrettyTables v2.4.0
[92933f4c] ProgressMeter v1.11.0
[295af30f] Revise v3.13.1
[10745b16] Statistics v1.11.1
[856f2bd8] StructTypes v1.11.0
[f8b46487] TestItemRunner v1.1.4
[1c621080] TestItems v1.0.0
[ac1d9e8a] ThreadsX v0.1.12
[37e2e46d] LinearAlgebra v1.12.0
[de0858da] Printf v1.11.0
[9e88b42a] Serialization v1.11.0
Info Packages marked with ⌅ have new versions available but compatibility constraints restrict them from upgrading. To see why use `status --outdated
As stated, Revise stop working (randomly).
Any ideas ?
Best,
Laurent