-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
vtk extension with vtk 9.0.3 works on 0.11.2 not on 0.12.0 (latest) #2562
Comments
I believe I was experiencing this bug, but upgrading to Panel v0.12.1 fixed it for me. With v0.11.3, A VTK-based pyvista rendering using the Panel backend would not load for me in Jupyterlab or VSCode. I don't have more details of the buggy environment, but here is my current working setup (for posterity):
|
Interesting, I didn't make any changes as part of 0.12.1 that would explain it being fixed now. |
Hmmm ... now that I try it out on an environment with 0.11.3, the Panel backend is working. There must be some other difference in my system that accounts for the change in behavior. I'll open an issue if my bug surfaces again reproducibly. Thank you! |
Should be fixed now (in Panel 0.12.4). |
Thanks for contacting us! Please read and follow these instructions carefully, then delete this introductory text to keep your issue easy to read. Note that the issue tracker is NOT the place for usage questions and technical assistance; post those at Discourse instead. Issues without the required information below may be closed immediately.
ALL software version info
(this library, plus any other relevant software, e.g. bokeh, python, notebook, OS, browser, etc)
Panel: 0.12.0
python : 3.9.6
pyvista: 0.31.3
vtk: 9.0.3
OS: Ubuntu 18.0.4 with xvfb installed.
Browser: Firefox 90.0.2 on OS: OSX Big Sur 11.4
environment.yml
Full environment from `conda list` with panel==0.12.0:
With panel==0.11.3:
Description of expected behavior and the observed behavior
Should show an interactive vtk.js render.
Complete, minimal, self-contained example code that reproduces the issue
From the example on panel's documentation :
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action
The text was updated successfully, but these errors were encountered: