Yep. And I've now updated to 4.63.0.
Awesome work! You’re killing it.Making good progress so far. Lot of stuff hardened, completely fresh new DB with query builder, new auth with multiple users and roles, tons of data fetching stuff fixed, and many other improvements.
Agents requiring more supervision than I initially expected and I have a bunch of other tasks I need to get done before tmr, so won’t be done today.
I also found two different libraries that might be able to solve the hard part of the automation rule builder @VideoDad brought up.
Going to redo a bunch of UI too. Might use this:
Overkill for this but really cool.
And it just locked up again. Here's the Container dashboard while it was unresponsive:I was running Docker Desktop << 4.62.0, but I just updated to 4.62.0, which is what prompted the restart of the container.![]()
Memory leak?
Docker-philes, is there a way to interrogate my container when it's in this stuck state? I can open a Terminal, but I'm unfamiliar with what I can or can't do, there. I did try "top" but it didn't do anything while it was stuck, whereas right now, functioning properly, "top" does report process usage.