-
when debugging an issue w/ writes to an LED controller, I saw that writing single values, e.g. `?color=ffffff`, worked (would write, and then read back the written value -- this could take a little bi…
-
https://github.com/vapor-ware/synse-sdk/blob/master/sdk/device.go#L272
this gets called a lot, so the logs get filled up quickly
```
time="2018-07-02T21:00:58Z" level=debug msg="[sdk] adding 12…
-
https://circleci.com/gh/vapor-ware/synse-cli/384
```
#!/bin/bash -eo pipefail
cd cmd/
gox --output="../build/${BINARY_NAME}_{{.OS}}_{{.Arch}}" -osarch='!darwin/386'
Number of parallel builds:…
-
## Description
synse server appears to fail transaction checks because of an issue in the sdk/plugin: https://github.com/vapor-ware/synse-sdk/issues/148
but when running end-to-end tests (the test…
-
I can't remember if this question was asked before, or what the answer to it was.
with an intentionally incorrect device config from the logging branch (https://github.com/vapor-ware/synse-sdk/pul…
-
in a PR where the build should have failed, it didnt. looking at the CI logs, I see that the error is there
```
#!/bin/bash -eo pipefail
make examples
examples/auto_enumerate/
github.com/vapo…
-
once synse 2.0 is released, the plugins stuff will need to be opened up as well (sdk, et al) which includes this, as this serves as the glue between synse-server and plugins.
once this is open sour…
-
I only see this when running the transaction_test.go file independently.
When all tests are run, some previously run test must have initialized it by creating a Plugin.
Root cause is that NewTra…
-
At startup when we do not find a known device prototype, we log a warning which is good. It would be useful to log the known device prototypes at info level.
May end up being here, but could be els…
-
## Description
It seems like when a device does not have any data (e.g. the plugin SDK fails to read anything off of a configured device) we either:
- get `"null"` back as the reading value in a val…