'pyvista-plot' directive for embedded-interactive viewers doesn't work for MultiBlock Objects about pyvista

[jourdain]

I think I know why...

Sorry to go into the details, but the remote setup use vtk-osmesa while the local one (working) is using regular vtk.
When the scene get serialized, we have a mapping between the server objects and the vtk-js ones. And I think the issue is that we are missing a mapping when the class is from osmesa vs xlib.

So to fix that issue we will need to properly register that missing class here, but for that we would need to get the name of the missing serializable class. Which you might be able to get it you do the following locally to run with osmesa

pip uninstall vtk
pip install vtk-osmesa --extra-index-url https://wheels.vtk.org

I think by default, you should see some log either on the python side or on the client side.
If it is on the client side, you might be able to know which class name is the culprit right away without any new testing.

HTH

[MatthewFlamm]

This looks like a duplicate of #5361 although this one more linearly describes the problem.

[evrose54]

@MatthewFlamm sorry for missing that issue you mentioned. Another important part of this I forgot to add is that the MultiBlock Object[s] is actually rendered correctly when I build and host my documentation locally. It's with the remote build/hosting that the MultiBlock object[s] isn't rendered at all. I'll attach two screen captures which show what I'm talking about. I built the documentation with the same example for both local and remote.

I also was able to remotely render the PolyData + MultiBlock objects fine using Trame, and they rendered appropriately using a custom embedded viewer I made which stemmed off of VTK's OfflineLocalView Example.

Here is the pyvista-plot directive used locally in the docs I built:

Screen.Recording.2024-03-21.at.9.27.36.AM.mov

And here is the same process done, only it's been hosted/rendered remotely.

Screen.Recording.2024-03-21.at.9.32.49.AM.mov