-
-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning when loading Plotly backend #4910
Comments
I also got this false warning julia> Pkg.status()
Activating project at `~\Kaggle\BirdCLEF2023`
Status `~\Kaggle\BirdCLEF2023\Project.toml`
[6e4b80f9] BenchmarkTools v1.5.0
[336ed68f] CSV v0.10.14
[717857b8] DSP v0.7.9
[a93c6f00] DataFrames v1.6.1
[864edb3b] DataStructures v0.18.20
[7a1cc6ca] FFTW v1.8.0
[5789e2e9] FileIO v1.16.3
[587475ba] Flux v0.14.15
[da1fdf0e] FreqTables v0.4.6
⌃ [e9467ef8] GLMakie v0.9.10
⌃ [9db2cae5] Gtk4 v0.6.1
[b13ce0c6] LibSndFile v2.4.0
[f1d291b0] MLUtils v0.4.4
[91a5bcdd] Plots v1.40.4
⌃ [96b87e3f] ReverseGeocode v0.5.0
[afe32e48] Sound v0.5.0
⌃ [2913bbd2] StatsBase v0.33.21
[f3b207a7] StatsPlots v0.15.7
Info Packages marked with ⌃ have new versions available and may be upgradable.
julia> plotly()
┌ Warning: Failed to load integration with PlotlyBase & PlotlyKaleido.
│ exception =
│ ArgumentError: Package PlotlyBase not found in current path.
│ - Run `import Pkg; Pkg.add("PlotlyBase")` to install the PlotlyBase package.
│ Stacktrace:
│ [1] macro expansion
│ @ .\loading.jl:1772 [inlined]
│ [2] macro expansion
│ @ .\lock.jl:267 [inlined]
│ [3] __require(into::Module, mod::Symbol)
│ @ Base .\loading.jl:1753
│ [4] #invoke_in_world#3
│ @ .\essentials.jl:926 [inlined]
│ [5] invoke_in_world
│ @ .\essentials.jl:923 [inlined]
│ [6] require(into::Module, mod::Symbol)
│ @ Base .\loading.jl:1746
│ [7] top-level scope
│ @ ~\.julia\packages\Plots\ju9dp\src\backends.jl:565
│ [8] eval
│ @ .\boot.jl:385 [inlined]
│ [9] _initialize_backend(pkg::Plots.PlotlyBackend)
│ @ Plots ~\.julia\packages\Plots\ju9dp\src\backends.jl:564
│ [10] backend
│ @ ~\.julia\packages\Plots\ju9dp\src\backends.jl:244 [inlined]
│ [11] plotly()
│ @ Plots ~\.julia\packages\Plots\ju9dp\src\backends.jl:87
│ [12] top-level scope
│ @ ~\Documents\Julia\Kaggle\BirdCLEF2023\1f_BasicExploration.jl:12
│ [13] eval
│ @ .\boot.jl:385 [inlined]
│ [14] include_string(mapexpr::typeof(REPL.softscope), mod::Module, code::String, filename::String)
│ @ Base .\loading.jl:2076
│ [15] invokelatest(::Any, ::Any, ::Vararg{Any}; kwargs::@Kwargs{})
│ @ Base .\essentials.jl:892
│ [16] invokelatest(::Any, ::Any, ::Vararg{Any})
│ @ Base .\essentials.jl:889
│ [17] inlineeval(m::Module, code::String, code_line::Int64, code_column::Int64, file::String; softscope::Bool)
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\eval.jl:271
│ [18] (::VSCodeServer.var"#69#74"{Bool, Bool, Bool, Module, String, Int64, Int64, String, VSCodeServer.ReplRunCodeRequestParams})()
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\eval.jl:181
│ [19] withpath(f::VSCodeServer.var"#69#74"{Bool, Bool, Bool, Module, String, Int64, Int64, String, VSCodeServer.ReplRunCodeRequestParams}, path::String)
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\repl.jl:276
│ [20] (::VSCodeServer.var"#68#73"{Bool, Bool, Bool, Module, String, Int64, Int64, String, VSCodeServer.ReplRunCodeRequestParams})()
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\eval.jl:179
│ [21] hideprompt(f::VSCodeServer.var"#68#73"{Bool, Bool, Bool, Module, String, Int64, Int64, String, VSCodeServer.ReplRunCodeRequestParams})
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\repl.jl:38
│ [22] (::VSCodeServer.var"#67#72"{Bool, Bool, Bool, Module, String, Int64, Int64, String, VSCodeServer.ReplRunCodeRequestParams})()
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\eval.jl:150
│ [23] with_logstate(f::Function, logstate::Any)
│ @ Base.CoreLogging .\logging.jl:515
│ [24] with_logger
│ @ .\logging.jl:627 [inlined]
│ [25] (::VSCodeServer.var"#66#71"{VSCodeServer.ReplRunCodeRequestParams})()
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\eval.jl:263
│ [26] #invokelatest#2
│ @ .\essentials.jl:892 [inlined]
│ [27] invokelatest(::Any)
│ @ Base .\essentials.jl:889
│ [28] (::VSCodeServer.var"#64#65")()
│ @ VSCodeServer ~\.vscode\extensions\julialang.language-julia-1.79.2\scripts\packages\VSCodeServer\src\eval.jl:34
└ @ Plots ~\.julia\packages\Plots\ju9dp\src\backends.jl:574
Plots.PlotlyBackend()
julia> versioninfo()
Julia Version 1.10.2
Commit bd47eca2c8 (2024-03-01 10:14 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: 16 × AMD Ryzen 7 4800HS with Radeon Graphics
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-15.0.7 (ORCJIT, znver2)
Threads: 6 default, 0 interactive, 3 GC (on 16 virtual cores)
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS = 6
|
Its not a false warning. You can plot in the browser without having these in the Project, but for saving figures via |
Is there a way to remove this warning? |
I think you can set the debug level in a way that warnings are not shown. Alternatively you can add Btw., that looks like a really nicely done course! |
I meant this: https://docs.julialang.org/en/v1/stdlib/Logging/#Logging.disable_logging
That refers to the version of PlotlyKaleido. As of Plots v1.40.8 that should be compatible with PlotlyKaleido v2. This is from the times Pkg couldn't handle version management of optional dependencies. Will be better in Plots v2. |
Alright, thanks a lot for your help! :) |
When creating a fresh environment with Plots.jl, the Plotly does not loading dependencies correctly, warning
When re-running
using Plots
andplotly()
, this warning is not thrown again.This surprised me since the backend docs state:
Related issues
Full error
The text was updated successfully, but these errors were encountered: