Mateusz Gozdek
Mateusz Gozdek
/remove-lifecycle stale
not stale :crossed_fingers:
Another use case I would see for that is rolling update of immutable infrastructure, where you just roll the update one server/resource at a time.
@prateekpandey14 I suppose this issue should be re-opened?
/remove-lifecycle stale
Just a note, if you use PIV module for GPG, e.g using https://github.com/alonbl/gnupg-pkcs11-scd, then you will still get notified properly.
Thanks for looking into it @blanquicet. Should I open a separate issue then if I would like `biolatency` to be available as a local gadget?
How about just having some default list of socket paths to probe and connect to first available (e.g. `/var/run/docker.sock` and `/run/docker.sock`) + being able to configure custom socket path for...
Yes, I did and it does not make a difference.