Bug #2322
time_precision Warning in log
Status: | Resolved | Start date: | 06/14/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Wienke | % Done: | 100% | |
Category: | - | |||
Target version: | Robotics Service Bus - rsb-0.13 |
Description
The logfile is filled with ~80-100 lines per second with messages like these:
[06/14/15 14:32:44] [WARN] time_precision=m will be disabled in future release, use time_precision=ms instead [06/14/15 14:32:44] [WARN] time_precision=m will be disabled in future release, use time_precision=ms instead [06/14/15 14:32:44] [WARN] time_precision=m will be disabled in future release, use time_precision=ms instead
Wasn't this supposed to be gone with the new version?
Associated revisions
History
#1 Updated by J. Wienke almost 8 years ago
- Status changed from New to Rejected
This is an upstream issue of the influxdb python API. Basically I can't do anything against this apart from manually patching that API or completely switching to influxdb 0.9, which could be possible now with the new grafana version. But that would require some work. :/
#2 Updated by J. Wienke almost 8 years ago
- Status changed from Rejected to In Progress
- Target version set to rsb-0.13
Hm, strange, seems I added this once on my own to work around some other bug.
#3 Updated by J. Wienke almost 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:graphite-adapter|f6e4ef44f9f52ad56d4367dbd2d2991fc5a70994.