You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
List of workers can be incomplete or it can contain workers that are not active anymore
To Reproduce
Start yggdrasil on Terminal 1: go run ./cmd/yggd --server tcp://localhost:1883 --log-level trace --client-id $(hostname)
Start echo worker on Terminal 2: go run ./worker/echo -log-level trace
Try to get list of workers on Terminal 3 using: go run ./cmd/yggctl workers list or busctl --user call com.redhat.Yggdrasil1 /com/redhat/Yggdrasil1 com.redhat.Yggdrasil1 ListWorkers
Current result
List of workers is empty. The worker gets into the list of workers only after receiving the first message from MQTT.
Expected behavior
List of running workers.
Something like this in the case of yggctl:
echo - DispatchedAt:
echo - Version: 1
Something like this in the case of busctl (or any other D-Bus app):
When worker has been stopped, then you can still see worker in the list of active workers despite MQTT message for the worker has been received and yggdrasil wasn't able to dispatch data from the MQTT message.
The text was updated successfully, but these errors were encountered:
Each worker is expected to own a name on the bus under the namespace com.redhat.Yggdrasil1.Worker1 (i.e. com.redhat.Yggdrasil1.Worker1.echo). When asked for a list of workers, yggd should enumerate all names on the bus, filter for names that begin with the namespace value above, and return the results.
Describe the bug
List of workers can be incomplete or it can contain workers that are not active anymore
To Reproduce
go run ./cmd/yggd --server tcp://localhost:1883 --log-level trace --client-id $(hostname)
go run ./worker/echo -log-level trace
go run ./cmd/yggctl workers list
orbusctl --user call com.redhat.Yggdrasil1 /com/redhat/Yggdrasil1 com.redhat.Yggdrasil1 ListWorkers
Current result
List of workers is empty. The worker gets into the list of workers only after receiving the first message from MQTT.
Expected behavior
List of running workers.
Something like this in the case of
yggctl
:Something like this in the case of
busctl
(or any other D-Bus app):Additional Information
When worker has been stopped, then you can still see worker in the list of active workers despite MQTT message for the worker has been received and yggdrasil wasn't able to dispatch data from the MQTT message.
The text was updated successfully, but these errors were encountered: