Ryan Joseph

Results 23 issues of Ryan Joseph

`REDIS_URL` handling needs to be fixed, is really the point.

code-smells-bad
P2

Ugh.

bug
code-smells-bad
P1
good-first-issue

Will require a re-thinking of sensor runlooping (and therefore is related to #3), as ideally any NMEA stream-producing sensor should act in a push-only manner rather than the current `sensor-src`-tick-based-pull...

enhancement
major-feature
P3
good-first-issue

Need to make this configurable and be sure it's setup to happen every so often (~once/week)!

bug
P0
good-first-issue

Redis 5.0 landed [the feature](https://redis.io/topics/streams-intro) that this code base half-implements! The examples in the docs are even sensor-based! Re-implement using streams, obviously. (Will need relatively wide adoption of v5, though)

enhancement
nice-to-have

On charlie, the forwarding invocations of this seem to be leaking quite badly over long periods (these have been running for about 9 days): ``` ryan 3038 0.1 17.1 2233072...

bug
major-feature
P0

It's going to have to happen someday...

enhancement
nice-to-have
P2

On a reboot, a device may have a localtime value that is stale from the last boot, and before the device updates time (from NTP) it can start publishing sensor...

bug
nice-to-have
P3

The `downsample` tool has grown far too ungainly as it has gained features (and still needs to gain another feature with the integration of the `thingspeak` forwarder, #8). It needs...

bug
major-feature
code-smells-bad
P3

Could even implicitly enable via a URL scheme for `-o` such as `thingspeak://WRITE_API_KEY@CHANNEL_ID`. Also, `downsample` *really* needs to be re-factored. ~Should probably file a separate bug for that...~: #10

code-smells-bad
P3