Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

quickvolshow and showvol crashes on VS Code #430

Open
goioCodes opened this issue Feb 24, 2023 · 3 comments
Open

quickvolshow and showvol crashes on VS Code #430

goioCodes opened this issue Feb 24, 2023 · 3 comments

Comments

@goioCodes
Copy link

I have been trying to make the package work on a VS Code notebook to no avail. Some of the things I tried did work in a Jupyter notebook after much testing. I performed all of the testing by only running the first 3 examples. quickscatter and quickquiver work correctly on VS Code, however running the quickvolshow example instantly crashes the application, triggering an "Are you sure you want to close without saving?" pop-up, which upon selecting any of the options does nothing and it is impossible to interact with the notebook any longer, requiring a full restart. I'm not sure whether this is a VS Code problem.

Here's everything I tried, none of the following options made quickshowvol work:

  • Default anaconda install using python==3.10.9, with ipyvolume==0.6.0 installed from conda-forge with the automatically downloaded dependencies. This results in pythreejs==2.4.1 since pythreejs==2.4.2 is not available on conda-forge. This hangs the kernel when executing any method on a jupyter notebook (includng quickscatter and quickquiver), but quickscatter and quickquiver work correctly on VSC.
  • Updating the installation to pythreejs==2.4.2 using pip. Everything works in Jupyter notebook, but only quickscatter and quickquiver work in VSC.
  • Installing ipyvolume with pip on top of a default anaconda installation, same as above (it works on Jupyter).
  • Downgrading to pythreejs==2.3.0 causes the quickscatter and quickquiver widgets to also not render correctly on VSC, they are missing all of the GUI elements on the right. Didn't test with Jupyter.
  • From empty environment using python==3.8, install with pip ipyvolume==0.5.2, matplotlib and ipython_genutils. Same as above.

Is there some way to get it working? Just in case, here's one of the environments that works in Jupyter notebook but still crashes VSC.
environment.yml.txt

@maartenbreddels
Copy link
Collaborator

Hi,

very strange behaviour. Can you try what happens in the Jupyter notebook? Maybe there is a driver issue. Which OS are you using?

regards,

Maarten

@goioCodes
Copy link
Author

goioCodes commented Feb 25, 2023

Hello,
I'm using Windows 10. As I said, the default anaconda install with ipyvolume installed from pip works perfectly fine on a Jupyter notebook, with no errors. The same exact code and environment however, will not work specifically on the quickvolshow example on VSCode.

I've done some more testing and I ran almost every example on the example page, including the male head example and lighting examples, and none of them caused a crash on VSCode. The only exception is the first volume example in this page. This points to a problem specifically with the quickshowvol and volshow functions.

I also found there are some error messages that appear on the VSCode developer tools console:
cap1
cap2
There are a lot of "Exception opening new comm" messages flooding the console when running anything related to ipywidgets, including a simple interact() slider and the working examples, so I'm not sure if they are related to this problem.

Edit: I re-run all the examples and now it looks like the last two examples from lighting are also crashing. To be clear, I'm sure the first of the two examples ran correctly the first time I tried. However I have not been able to make it work again even after creating a new notebook.

@goioCodes
Copy link
Author

May be related to #microsoft/vscode-jupyter#4525. I opened a remote Jupyter server and connected to it using VSCode, and everything worked! So this is probably a VSCode issue. I'd like to open an issue there, any tip on how I may go about it?

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

No branches or pull requests

2 participants