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

Getting unique column values sometimes throws error #709

Closed
alexsielicki opened this issue Mar 31, 2017 · 1 comment
Closed

Getting unique column values sometimes throws error #709

alexsielicki opened this issue Mar 31, 2017 · 1 comment
Assignees
Labels

Comments

@alexsielicki
Copy link
Collaborator

alexsielicki commented Mar 31, 2017

Asking for unique column values using the get_model_arrayset_metadata API sometimes throws an error for string columns. This might be cache related. Seems to be due to sometimes part of the result coming back as a list object instead of the anticipated numpy.ndarray object. I added a bandaid for now, but this should be properly fixed, probably by @Mletter1. Here's the temp fix I added on the bugfix branch (where I'm working on timeseries coloring by string variable):
bbb61cd

@Mletter1
Copy link
Collaborator

Mletter1 commented May 3, 2017

change to isinstance()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants