Jonathan Davies
Jonathan Davies
This just failed again, there's definitely a regression between `1.16.3-gke.1` and `.401`.
Indeed, `1.16.13-gke.1` and `.401` - sorry. I upgraded the cluster to `regular-channel/1.17.9-gke.1504` last Friday and it seems to have not had this issue so far.
I was debugging a coturn server I run today, when I noticed that the `openssl` client I was using was talking TLS1.3 to it? ``` $ openssl s_client -connect turn.test:5349...
Every single IPv6 socket out there is simultaneously a IPv4 socket. Just have the exporter bind on `[::]:9167` and it'll be on both.
It also depends on the zoom level, past a certain point `neighbourhood` isn't shown: 
I've had to go around and disable autodoc on all my now Flask-1.0.2 microservices.
@nosnilmot I reverted the changes, but I still feel they fit better with the documentation change as everything is consistent that way.
I decided to try this patch on one of my systems, there seems to be a special case for `/dev` and `/sys` that exa doesn't handle: ``` $ ls -lZ...
I can confirm that b4504f9 is working fantastically on my SELinux enabled systems.
> how does QubesOS hand out IPv6 addresses? It appears to be using IPv6 link and unique local addresses handed out by Xen. > I.e. (a) how is the firewall...