Maarten Breddels

> `Solara server is starting at http://localhost:8765` It is binding to localhost, so that means it only binds to the loopback device, if you pass `--host 0.0.0.0` it will bind...

The relevant part of the logs: ``` self = def flatten(self): if self.dtype == object: return self # already flat > keys = self._internal.key_array() E RuntimeError: pybind11::handle::inc_ref() PyGILState_Check() failure. /opt/hostedtoolcache/Python/3.9.20/x64/lib/python3.9/site-packages/vaex/hash.py:78:...

it's yanked

I could not reproduce this on a local ubuntu machine with Python 3.11, but i'll continue to see if I can reproduce it (help is welcome)

Update: We do not build with `-DNDEBUG` when we use cibuildwheel, but in a regular build we do pass this to the compiler. This causes our release to be shipped...

See https://github.com/vaexio/vaex/pull/2440

Hi Daniel, if you store in reactive variables, they are per 'user' (or kernel rather). It's up to the libraries that you use the provide that flexibility to be able...

We could do very complicated workarounds, but I have to say I find it a bit strange that this packages does not support this. It means that this package can...

If you want multiple environments, with different solara servers I would just run multiple servers and but nginx in front of it. In the jupyter world, the jupyter server is...

This should go upstream one day, but you can fix that using what I have in [vaex](https://github.com/maartenbreddels/vaex/blob/2790103ad510ce8574f61856b38edcc173792a06/vaex/notebook/utils.py#L14): ```python from vaex.notebook.utils import debounced ..... slider.observe(debounced(delay_seconds=0.1)(on_value_change), names='value') ``` The weird syntax is...