Closed StevenWarmelink closed 1 year ago
If I change the following lines from us
to ns
or remove the datetime
conversion, I can get the code to work.
Thanks for looking into this @Hoxbro !
From what I've seen after some debugging geom_aggregate._process
is called twice, the first time it updates the dataframe referenced aselement.data
by converting the relevant datetime columns to int, the second time it tries to do so again but fails.
Questions are:
geom_aggregate._process
expected?element.data
? I find that somewhat surprising.I could fix the issue by adding these two lines above the failing code.
if xtype == 'datetime' or ytype == 'datetime':
df = df.copy()
The traceback reported in this recent blog post is very similar to the one reported in this issue. They have the same root cause and will certainly have the same fix. Specifically the blog post is plotting a QuadMesh, and the issue lies in quadmesh_rasterize
instead of geom_aggreate
.
ALL software version info
pandas==1.3.5 holoviews==1.14.8 bokeh==2.3.3 python==3.8.5
Description of expected behavior and the observed behavior
When rasterizing multiple hv.Rectangles, I expect to be able to supply Timestamp coordinates; this works fine without the rasterization or for single Rectangles. However, when multiple Rectangles with Timestamp coordinates are rasterized, the supplied timestamps are out of bounds.
EDIT: This also occurs when a single rectangle is supplied in a list when calling hv.Rectangles.
Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action