Good evening @pierre-gilles
That’s the same.
A regression (the bug had already been fixed, it seems to me)
@pierre-gilles,
I tried, and by removing what you fixed in June it works again for me
I second that. I posted in the update announcement thread before seeing your messages…!
Indeed, same here on my end and with Gladys+ as well…
Can someone create a GitHub issue?
Edit: I moved the thread, and I closed the other one
You really need to create new threads; long, drawn-out threads are really complicated ![]()
Yes, you’re right, we got a bit scattered!
I’ll take care of creating the issue
So the issue and the PR
thanks @_Will_71
Thanks for the PR! Indeed it fixes the problem, but in my opinion the root cause is deeper than that — I wouldn’t be surprised if we see the issue resurface in the future.
I think the problem comes from a Preact bug; I found this GitHub issue while searching a bit:
https
It’s clear that it’s not normal to have to modify it like that. Worth keeping an eye on.
I just deployed the fix on Gladys Plus (since it’s a frontend fix, it’s available right now on Gladys Plus)
A Gladys local version will arrive later ![]()
good evening @pierre-gilles
It works for me, thank you very much
Bug fixed in Gladys Assistant 4.31.1 :

