-
**Describe the bug**
Deploying a fresh install of Openshift 4.15.22 and deploying the external-secrets-operator like usual (via gitops process). But, recently i started getting this error on the 'ex…
-
Right now, timestamps are "today" or a date.
How would you feel about using relative timestamps (x [block]s ago) that on mouseover provide the exact RFC3339 timestamp? Something like this https://g…
-
Please answer these questions before submitting your issue. Thanks!
### What did you do?
[ttps://play.golang.org/p/BItq172M-_](https://play.golang.org/p/BItq172M-_)
The bad time string "0007-05-3…
-
It appears this is controlled using `x-ms-code-generation-settings` -> `useDateTimeOffset` (from `./specification/synapse/data-plane/Microsoft.Synapse/preview/2019-06-01-preview/artifacts.json`):
`…
-
Hi, this plugin was working for me but since a week ago I only get the following:
{ [-]
error_message: bad query: error parsing end time: must be unix timestamp or rfc3339 string
http…
-
## Feature Request
**Can you support different format definition for the time type?**
For now, the time format is fixed with RFC3339,more format definition is better.
Thx!
-
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…
-
Hello!
Currently it's assumed that attribute can have only one type and this case doesn't work.
Example of my schema.
``` json
{
"id": "/some_controller.rb",
"properties": {
"some_timestam…
-
__Issue description:__
There is an issue on TSDB side with handling incoming `Flux` queries which contains negation operators in its body (`!=` or `!~`). Sometimes, the results of such queries exec…
-
The format used by JSON Schema for date-time is RFC3339. That's the format I've used for that field when designing the schema.
https://github.com/BSData/schemas/blob/492c60786fadf3c3b206f32c6637602…