Vladimir Skipor
Vladimir Skipor
Currently, logger with `trace()` option prints standart exception traceback. But sometimes, it's better to see full exception trace, that contains frames before `try/except` block. Or see the traceback, even there...
Problem: shoot timings with 10ms sleep gun, phout aggregator, have peaks up to 125ms. Latency peaks corelate with iowait peaks in monitoring. Theory: latency peaks are caused by aggregator sample...
```go const debugChecks = tag.Debug // On true, checks fields order, types, and constraints (string has no whitespaces for example) type FildType int const ( IntType FieldType = iota Float32Type...
Blocked by #93
Use [Cobra](https://github.com/spf13/cobra) as CLI, and integrate is with Viper, which is already used for configuration. That allows redefining config keys by CLI flags.
https://docs.scipy.org/doc/numpy/neps/npy-format.html https://github.com/kshedden/gonpy https://github.com/sbinet/npyio Blocked by new format of HTTP samples
Counting coverage for sub packages too. https://www.ory.am/golang-go-code-coverage-accurate Coverage for acceptance tests: https://www.cyphar.com/blog/post/20170412-golang-integration-coverage https://www.elastic.co/blog/code-coverage-for-your-golang-system-tests
Every plugin implementation can have it's own defaults. But user still needed to set 'type' field for every plugin. I propose to add default `type`s for every plugin.
Current metrics reporting is very ugly. I propose to use [rcrowley/go-metrics](https://github.com/rcrowley/go-metrics) with json HTTP reporter.