-
When a bearer token is used to call tr1d1um APIs, the token is successfully propagated to scytale. However, scytale does not further propagate the bearer token to Talaria.
cc: @Sachin4403 @schmidtw…
-
Talaria should provide a metric that shows the configured number of `maxDevices` so it is easy to see via metrics.
-
Hi,
Followed with scytale issue https://github.com/xmidt-org/scytale/issues/350, the default talaria port is 6200, and I modify it to 6400 (for meet talaria.yaml), and restart again.
My CPE parodus…
-
For scalability inside kubernetes, talaria should register twice with consul. Once with the kubernetes dns for scytale and one with external dns so devices can connect to the instance via petasos.
-
```
panic: Base level can't be zero.
goroutine 935 [running]:
github.com/dgraph-io/badger/v3.(*levelsController).fillTablesL0ToLbase(0x400091e4d0, 0x4000837770, 0x4000837400)
/go/src/tal…
-
The config was designed to be live-loaded. However, it is a local variable inside the `main function` [here](https://github.com/kelindar/talaria/blob/master/main.go#L47)
-
The connection information (SessionID, trust, and time connected) should be added to all wrps that go through talaria, which means talaria has to re-encode every message.
Is the connection ID uniqu…
-
As WRP message come from the devices through Talaria or messages about devices come from Talaria, the Talaria server needs to enforce the correct value of trust. To do this, Talaria must overwrite th…
-
Dependent on https://github.com/xmidt-org/wrp-go/issues/53.
If the device sends Talaria a WRP with an empty Device ID field, Talaria should fill it with what it believes to be the Device ID of that…
-
Add some metrics for socket close:
- whether or not talaria initiated closing the socket
- reason for close given by device
- reason for close given by talaria
the reasons for close should proba…