Florian Klink
Florian Klink
I'd like to bind `josh-proxy` to a unix socket, or even use [systemd socket activation](https://systemd.io/FILE_DESCRIPTOR_STORE/), so I can lazily start josh-proxy on the first connection. This seems to be well...
As described in https://github.com/systemd/systemd/pull/5529#issuecomment-1105770011, `ip addrlabel` can be independent of a specific device / `.network` / `.link`. It's a bit annoying/confusing this is only accessible from a matching `.network` file....
**(1) Issue/Bug Description:** Windows started opening sometimes as if they were zoomed-in way too much, and don't "fit" into their boundaries they should be using. Probably started happening with GNOME...
## Proposed Commit Message ``` In a cloud environment, sometimes disks will attach while cloud-init is running and get missed. This adds a configurable timeout to wait for those disks....
This uses crate2nix to build rusty-jwt-tools. ## Checklist - [ ] Add a new entry in an appropriate subdirectory of `changelog.d` - [ ] Read and follow the [PR guidelines](https://docs.wire.com/developer/developer/pr-guidelines.html)
This will cause a libprom.pc file to be emitted during build, allowing downstream users to query linker/include flags via pkg-config.
It'd be great if you'd support moto 5.x. moto 5 brings some API changes, but seems to be much simpler overall.
I'm using the `cluster` external label to distinguish metrics/logs pushed from several clusters. The `cluster` label seems to get derived from the namespace and resource name of the `GrafanaAgent` resource....
Far too often, I realized some metrics were missing, because grafana-agent had no permissions to access the target (https://github.com/grafana/agent/issues/1186), or because some paths were wrong. I don't really want to...
It should be good practice in 2018 to validate SSL certificates by default, and require the user to disable this explicitly if a validation should NOT be performed.