Tom Pike

> @tpike3 - I just updated to jupyterlab 4.3.2 and see the same behavior. > >  HMMM @nicolas-starck can you share your iypthon ipyvue ipvuetify and solara version I...

Ahhh got it, now I remember I need to document this. You are in the pre-release version of ipyvue and ipvuetify You want to uninstall and then use ipyvue ~1.11.2...

> Can we pin those dependencies ` > Also @maartenbreddels is this incompatibility a known issue over at Solara? Yes we should do that, just need to remember to undo...

Partially addressed in #2510 still need to update pyproject.toml

@katia-sentry It looks like this takes our codecov results and uploads them to codecov, is that accurate?

@SqueshSvyt Cold you fix the failing checks please. (Apologies for the delay)

> Thanks for translating! The PR is appreciated. > > However, currently it changes too much unnecessarily. I'm also not fully convinced of changing such a classic, well defined model,...

Sorry for the delay --- very cool wrapping this in the SolaraViz! Only concern is the build is failing  I lost the thread of the conversation is the intro...

> Okay so I tested this by building a viz app for [geo_sir](https://github.com/projectmesa/mesa-examples/tree/main/gis/geo_sir) > > ... > > self._id_to_agent[i] for i in self._idx.intersection(geometry.bounds) > ~~~~~~~~~~~~~~~~~^^^ > KeyError: 2287846026144 > ```...

@EwoutH I think the problem is here --[mesa-geo agents property](https://github.com/projectmesa/mesa-geo/blob/4e22c5c295048c4faa90531c19a08c5a9fce59ee/mesa_geo/geospace.py#L256) This is using agents as a property and may be causing a collision with agents in Mesa now. Mesa-geo creates...