Regression between version 13.18.0 and 13.18.1

[xavArtley]

Hello,

I think it will be hard to debug and I'll try to add as much as information its needs but I experience a regression under panel python library which are related to changes introduced by version 13.18.1

panel serialize a python vtkRenderWindow and use vtk.js synchronizableRenderWindow to reconstruct it and display the vtk scene in the browser.

However on panel side we developped some utilities as the possibility to add an orientationWidget in the scene.

Everthing worked well until version 13.18.1 where the following error appeared.

Uncaught (in promise) TypeError: Cannot read property 'offset' of null
    at Object.e.setMapperShaderParameters (VM273 vtk.js:282)
    at Object.e.updateShaders (VM273 vtk.js:282)
    at Object.e.renderPieceDraw (VM273 vtk.js:282)
    at Object.e.renderPiece (VM273 vtk.js:282)
    at Object.e.render (VM273 vtk.js:282)
    at e.opaquePass (VM273 vtk.js:282)
    at Object.e.apply (VM273 vtk.js:282)
    at Object.e.traverse (VM273 vtk.js:282)
    at e.traverseOpaquePass (VM273 vtk.js:282)
    at Object.e.traverse (VM273 vtk.js:282)

As long as I don't add objects on javascript side and stick to rendering the serialized scene everithing run smoothly.
It's the mix of both serialize scene and other actor added on javascript side directly wich make the error occur

[boucaud]

Hello,

Do you have more details on the way this orientation widget is created ? The example seems to work as expected.
Thanks !

[xavArtley]

The error occur only when a scene is updated in the vtkSynchronizableRenderWindow

Here is an example of the error in action

First I create a renderWindow with a only a Cone and I an orientation widget is added on javascript side:
The python scene is serialized and passed to javascript side (everything is working)

Then I add a Sphere to the scene and I synchronize with javascipt side and the error occur

[xavArtley]

I tried to put a reproducible example

It's not well coded it's just a bunch of copy past but it allows to reproduce the error:
https://drive.google.com/file/d/1M9aLkFTDk20DnqLM7J5azrs-vrae8Q0i/view?usp=sharing

[boucaud]

Thank you for your example. I will try to check as soon as I can

[jourdain]

Thanks @boucaud for looking into it.

[jourdain]

If this is still an issue, please re-open.