Joel Pearson

I've added this to my `~/.bashrc` ``` if [ ! -S /tmp/wsl-ssh-pageant.socket ] && [ -z "$TMUX" ]; then echo "Starting socat relay to ssh-pageant" tmux new-session -d -s socat-ssh-agent...

You could run Zalenium inside kubernetes instead. Then the docker version won’t matter anymore as long as it’s compatible with whatever Kubernetes flavour you choose.

@iandeveseleer Ahh yes the fabric8 client is a bit older. I have an installation running on Kubernetes 1.11. What happens after 1.16 which makes it not work? Zalenium doesn’t use...

> Hi, is it in the plans to fix this? It would be great can update to Docker 20, but we're stuck on 19 because of this bug. > Thanks...

Zalenium already supports basic auth. You shouldn’t need to be modifying any nginx config. You just need to enable the basic auth support in Zalenium. See https://opensource.zalando.com/zalenium/ Look for the...

Oh that's interesting. Will leave this open then. I'm sure you are aware that development has stopped on this project, so it isn't going to be fixed on its own.

There is some debugging you can enable, that I think we probably should have left enabled by default. If you see this file: https://github.com/zalando/zalenium/blob/master/src/main/resources/logback.xml#L23 You need to change that line...

Regarding that exception you posted, I'm pretty sure that doesn't matter because the selenium pods retry registration if it fails from memory.

I'm setting the SQL query from the UI

I trawled through the logs looking for the error, and I found this: ``` 2024-01-13 11:11:11.437 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.shower_humidity_5_min_ago fails Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py",...