Skip to content
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 "Chart elements should only be supplied a single kdim" #4912

Closed
hyamanieu opened this issue Apr 28, 2021 · 2 comments · Fixed by #4914
Closed

Warning "Chart elements should only be supplied a single kdim" #4912

hyamanieu opened this issue Apr 28, 2021 · 2 comments · Fixed by #4914
Milestone

Comments

@hyamanieu
Copy link
Contributor

ALL software version info

latest holoviews 1.14.3 and anything used to build the doc: http://holoviews.org/reference/streams/bokeh/Selection1D_tap.html

Description of expected behavior and the observed behavior

This example from the doc should show no warning.
It shows:

WARNING:param.Scatter: Chart elements should only be supplied a single kdim
WARNING:param.Scatter: Chart elements should only be supplied a single kdim

It is hard to decipher where it is from.

My own model is also using a holoviews.stream object and since update, shows this very same warning. Previous version was 1.13.3.

Complete, minimal, self-contained example code that reproduces the issue

http://holoviews.org/reference/streams/bokeh/Selection1D_tap.html

@philippjfr
Copy link
Member

In the example it's because of this:

points = hv.Scatter(data, ['Date', 'r2'], ['block', 'id']).redim.range(r2=(0., 1))

which should be updated to:

points = hv.Scatter(data, 'Date', ['r2', 'block', 'id']).redim.range(r2=(0., 1))

@hyamanieu
Copy link
Contributor Author

Alright, i'll submit a PR for this example this week.

hyamanieu added a commit to hyamanieu/holoviews that referenced this issue Apr 30, 2021
philippjfr pushed a commit that referenced this issue May 17, 2021
@philippjfr philippjfr added this to the v1.14.4 milestone May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants