You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is partially the same issue as #4129, but I'm creating a new issue with a more descriptive title, more info on the problem including some version bisecting and a workaround that may be helpful. There may also be a separate problem related to #3623, JuliaPlots/StatsPlots.jl#442 and the PR #3751 - these issues may have been prematurely closed as fixed.
Details
This is the part that is the same as #4129. This particular error was introduced sometime between Plots v1.22.5 and Plots v1.23.6.
The error can be bypassed by defining a new Base.length() method for iterators. But this exposes another problem that may or may not be related:
julia> Base.length(f::Iterators.Flatten) = sum(length, f.it)
julia> bar(rand(3), color=[:red, :green, :blue]) # now produces a plot but with outlined bars without color fill
Again, the above has been the behavior since Plots v1.23.6. Versions of Plots between v1.11.0 - v1.22.5 did not have the iterator error, but instead produced several warnings like ┌ Warning: Indices Base.OneTo(3) of attribute *seriescolor* does not match data indices 1:17. and the resulting bars were all colored red (instead of white like now). The last working version with colored bars was Plots v1.10.6.
I also notice that Plotly doesn't have a line in the backend issue template just below (I entered it manually). Is Plotly no longer supported or is it just assumed identical to PlotlyJS? In any case, I wish Plotly would become a first-class citizen of Plots after v2.0 is released. For me it's by far the most interactive and easy to use backend.
Backends
This bug occurs on ( insert x below )
Backend
yes
no
untested
gr (default)
x
pythonplot
x
plotly
x
plotlyjs
x
pgfplotsx
x
unicodeplots
x
inspectdr
x
gaston
x
Versions
Plots.jl version: see above
Backend version (]st -m <backend(s)>): PlotlyBase v0.8.19
Output of versioninfo():
Julia Version 1.9.1
Commit 147bdf428c (2023-06-07 08:27 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: 16 × AMD Ryzen 9 6900HX with Radeon Graphics
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-14.0.6 (ORCJIT, znver3)
Threads: 14 on 16 virtual cores
Environment:
JULIA_EDITOR = "C:\Users\niclas\AppData\Local\Programs\Microsoft VS Code\Code.exe"
JULIA_NUM_THREADS = 14
JULIA_PKG_DEVDIR = C:\Stuff\Julia
The text was updated successfully, but these errors were encountered:
I also notice that Plotly doesn't have a line in the backend issue template just below (I entered it manually). Is Plotly no longer supported or is it just assumed identical to PlotlyJS?
They share most of the code, yes.
In any case, I wish Plotly would become a first-class citizen of Plots after v2.0 is released.
If you'd like to help with that, we can have a chat. Currently the position of a maintainer for the plotly stack is vacant.
This is partially the same issue as #4129, but I'm creating a new issue with a more descriptive title, more info on the problem including some version bisecting and a workaround that may be helpful. There may also be a separate problem related to #3623, JuliaPlots/StatsPlots.jl#442 and the PR #3751 - these issues may have been prematurely closed as fixed.
Details
This is the part that is the same as #4129. This particular error was introduced sometime between Plots v1.22.5 and Plots v1.23.6.
The error can be bypassed by defining a new
Base.length()
method for iterators. But this exposes another problem that may or may not be related:Again, the above has been the behavior since Plots v1.23.6. Versions of Plots between v1.11.0 - v1.22.5 did not have the iterator error, but instead produced several warnings like
┌ Warning: Indices Base.OneTo(3) of attribute *seriescolor* does not match data indices 1:17.
and the resulting bars were all colored red (instead of white like now). The last working version with colored bars was Plots v1.10.6.I also notice that Plotly doesn't have a line in the backend issue template just below (I entered it manually). Is Plotly no longer supported or is it just assumed identical to PlotlyJS? In any case, I wish Plotly would become a first-class citizen of Plots after v2.0 is released. For me it's by far the most interactive and easy to use backend.
Backends
This bug occurs on ( insert
x
below )Versions
Plots.jl version: see above
Backend version (
]st -m <backend(s)>
): PlotlyBase v0.8.19Output of
versioninfo()
:The text was updated successfully, but these errors were encountered: