thebestnom

Do you mind adding a test future releases would not break this?

Any news on this?

That's wierd... There shouldn't be a new neo4j session, Im pretty sure chrome network panel has which line of code generated the websocket, I checked the code and I did...

Also checked I did close session when used, that's why the websocket still open?

This is really wierd, it looks like driver bug as I do close this session onComplete, Ill test that out later this week

Also for just changing color I would not suggest reloading the entire network, you can get the id from viz.nodes.get and change the data there

In the second one, yes, in the original you only called reload 😅 anyway Ill test why the session doesn't close even though I call close probably tomorrow

@mdopp that's a bug 😅 but it shouldn't affect the websocket as the event doesn't add any session to the neo4j

I don't fully understand what you did to test that, render function us the main function so likely you'll find it slow there, but I don't understand what you mean...

Also mind sending your configuration? A lot if cypher in the config may slow down the render