Closed sztal closed 1 month ago
If I understand you correctly, this is fixed in https://github.com/holoviz/holoviews/pull/6145 (not yet merged):
Current behavior:
Great, thanks, I hope this will solve the issue. However, I still do not understand what makes any of the axes continuous? The two grouping variables are clearly discrete.
The bug was discovered and fixed in the PR. So, it is not directly related to the title.
See https://github.com/holoviz/holoviews/pull/6145/files#r1589356958
As in the title
ALL software version info
(this library, plus any other relevant software, e.g. bokeh, python, notebook, OS, browser, etc)
Description of expected behavior and the observed behavior
hv.Bars
should display x-tick values correctly in all cases instead of making some random errors from time to time in a way which is completely unpredictable.Complete, minimal, self-contained example code that reproduces the issue
For
df1
it works.But for
df2
it does not work correctly for some mysterious reasons. Note that the lower values for x-ticks are incorrect (both groups are labelled as "Pragmatic" which is a value ofstance
variable notcommunity
) and display one of the levels ofstance
variable instead of displaying values ofcommunity
column (`"Concerned" and "Informants").Please explain to me what is going on here, because it is extremely confusing. I really want to love
holoviews
because it has a lot of killer features, but sometimes it behaves in so cryptic unpredicable ways that makes it really painful to work with it.Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action