-
Websocket device names are hardcoded to
'WebsocketClientPseudoDevice'
("websocket_client_device_impl.cpp)
The streaming protocol has no meta option to set the device.info.name.
-
### Is your feature request related to a problem? Please describe
When replacing monitoring from Prometheus to Victoria Metrics, I cannot read the metrics of applications running in Mesos-Marathon du…
-
### Steps to reproduce
1. Attempt to auto configure an email provided by spacemail.com
### Expected behavior
Email should auto configure properly as done with all other email clients.
### …
-
### The problem
I have a Home Assistant installed on raspberry 4 with os Home Assistant image, the software work, but I have a problem on the setup of WiFi connection.
The wlan discovery work, but w…
-
## User Stories
_"As a VFS Team member, I need to know the information on the External Service Integrations
is up-to-date and complete, so that I can build on va.gov with confidence"_
## Issue Descri…
-
### Is this the right place to submit this?
- [X] This is not a security vulnerability or a crashing bug
- [X] This is not a question about how to use Istio
### Bug Description
Since Wednesd…
-
I'd like to raise a concern with including CIBA in the OAuth Flow Object in 3.2.0.
I understand that CIBA can, feasibly, be implemented using bare OAuth 2.0 but realistically it's an OpenID Connect…
-
Use case :
Service discovery like Consul can expose a whole lot of useful information using tags and metadata (host flavor, host os, runtime version, ...) however adding dozens of meta label to eve…
-
To eliminate the need for the application to be able to access the K8S API server we should provide a `ServiceDiscovery` implementation that does not rely on the use of the API.
We could do this by…
-
currently it seems this is broken on Home assistant 2024.9
(at least for me it doesn't work anymore).
The UDP discovery packets should be sent already.
Maybe its just my configuration, maybe it's a…
cl0rm updated
1 month ago