-
there are many ways in which a plugin could fail, and we need to make sure that they handle failures appropriately and uniformly.
to do that we need to know what 'appropriate' is.
basically, w…
-
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…
-
## 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…
-
https://circleci.com/gh/vapor-ware/synse-amt-plugin/34
CI fails to release if there are no previous tags. It fails around:
```
--since-tag $(git describe --abbrev=0 --tags `git rev-list --tags --sk…
-
`urfave/cli` contains the notion of "command groups" mostly to help divide logical groups of commands, which may be at the same level, in help text for users. We currently use this for `Synse Server A…
-
## Description
I noticed this a little while ago, just getting to opening the issue now.
When I was playing around with k8s configs for synse server, we had the service's `clusterIP` field as `Non…
-
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'm sure that this isn't at all a problem, but after seeing the help text over and over I can't help but feel that it could be simplified a little bit. For example, removing the
```
VERSION:
0.…
-
In the same context as #2, still playing around with `write`.
With an invalid argument like this
```
{
"1": 1
}
```
it returns `500`, which is what we expect:
```
{
"http_code": 500,
…
-
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…