-
### Describe the bug
The 32 bit seconds-since-unix-epoch format used by the uhlc crate, based on the 32 bit seconds in NTP, will roll over in only 12 years (2036). I've seen in a few places on the in…
-
The calendar vocab doesn't take leap seconds into account
``` factor
"2015-07-01 00:00:00Z" rfc3339>timestamp
"2015-06-30 00:00:00Z" rfc3339>timestamp time-
! T{ duration f 0 0 0 0 0 86400 }
``…
-
I am able to get
```
data.event_type:StandardMgaQuoteIssued OR data.event_type:QuoteIssued
```
query to work, but I cannot get a term set query to work, like
```
data.event_type:IN [StandardMg…
-
__Steps to reproduce:__
More details in this [forum topic](https://community.influxdata.com/t/two-tables-returned-with-identical-group-keys/28896/5)
1. I'm using a rollup task to write data to…
-
### Expected behavior
The line below in configuration file should produce rfc3339 timestamp string with milliseconds at least (it is assumed, because docs says - timegenerated is always high-precisio…
-
Hello @Empty2k12
Great crate, thank you. Recently I used this crate.
`let write_query = Timestamp::Now.into_query("weather").add_field("humidity", 82);`
`let write_result = influxdb.query(&wr…
-
I am porting my program from `chrono` to `time`. One thing I am stuck with is serializing a `Vec` with the `rfc3339` format.
This seems like a small but very useful addition. Is this something that…
-
Neither the parser nor the unparser provides any useful way to distinguish between .1, .01, .001 and so on, while RFC3339 allows any number of digits there.
-
Hello team,
I end up with a strange bug, when I was testing aggregation of resources I found that the `prometheus` format was missing some resources.
Here is the output for other format:
```
o…
-
Code like this:
```
Instant instant1 = Instant.parse("2020-03-06T08:14:01Z");
CloudEvent ce1 = new CloudEvent(type, version, source, instant1, null);
```
will run ok.
But code like this
…