-
once all the work is done to bring synse-server to parity with sdk 1.0, the user guide/api doc will need to be updated appropriately.
-
The problem is that the model is in all of the proto files.
Currently we can either lie about the model and make it common for all SNMP devices (sounds like a bad idea), or we can write separate ha…
-
when doing integration work with synse server, I noticed that the timestamp fields for the existing periodic health checks were not initially populated, but after a little while they showed up. to me,…
-
see: https://github.com/vapor-ware/synse-sdk/issues/248
essentially, we should have an option for discovering services automatically, instead of having them encoded into config the way we do now. t…
-
this can help to serve as an example for other repos as well.
-
It may be benign (?) but looks bad.
Line is:
ERRO[0000] devicesFromConfig. error from ParseDeviceConfig stat ./config/device: no such file or directory
Repro:
```
[mhink@ion ~/go/src/github.c…
-
I [updated the emulator plugin](https://github.com/vapor-ware/synse-emulator-plugin/tree/sdk-1.0) to use the sdk1.0 changes and once updated, got this output:
```
edaniszewski ~/go/src/github.com/va…
-
Settings, Network, AutoEnumerate, Context at least. Probably the strings as well.
(Pass by value)
https://github.com/vapor-ware/synse-sdk/blob/master/sdk/config/plugin.go#L17-L25
```
// Plugin…
-
For me, the logging output is a bit of a headache, partially because of #164 but also because the log output is difficult to do something with unless you have intimate knowledge of where things are in…
-
had a brief conversation last week w/ @timfallmk and we agreed that it would be nice to have some sort of auto-discovery option for synse/plugins.
v1.0 would be a good place to add that in, it see…