search

lux-org / lux

Automatically visualize your pandas dataframe via a single print! 📊 💡
Apache License 2.0
5.15k stars 365 forks source link

Are Binder examples working? #399

Closed michaelaye closed 3 years ago

michaelaye commented 3 years ago

In both Safari and Brave on iPad, and Firefox on Desktop, when I click on the Toggle pandas/lux button, all that happens is that the cell output is toggled away, no lux plots appear. Thinking it might be slower execution on Binder, I waited 2 minutes for something to appear, but nothing happened. I also tried the 2nd gallery example with the same issue. No errors shown either.

dorisjlee commented 3 years ago

Hi @michaelaye, Thank you for reporting this issue. Lux currently only support Chrome for Desktop, we have not tested this extensively for other browsers like Firefox or Safari. Let us know if it works if you try this on Chrome.

michaelaye commented 3 years ago

I didn't see that in the README, will try on Chrome.

michaelaye commented 3 years ago

ugh, not even Chromium? It has to be Chrome?

michaelaye commented 3 years ago

Tried Chromium, Brave, and Chrome now, still not working, no other plots appear when I click toggle in cell [4]. This is what I'm trying: https://hub.gke2.mybinder.org/user/lux-org-lux-binder-6ctrukf7/notebooks/demo/cars_demo.ipynb

dorisjlee commented 3 years ago

Ah I see, it looks like the Jupyter Notebook link is not working (related to #372). Could you please try this Binder link for the JupyterLab version instead? Let me know if you are still seeing issues with this. Thanks!

michaelaye commented 3 years ago

I'm getting this error shown:

FileNotFoundError: Could not find package.json under dir /srv/conda/envs/notebook/lib/python3.7/site-packages/luxwidget

image

michaelaye commented 3 years ago

at the end the JLab was actually loading. But led me to the next thing not working (new issue).

dorisjlee commented 3 years ago

Thanks for reporting this. You're right that this seems like the same issue as #372. Closing this for now, but we will look into resolving issue #372 soon!