-
Elastic cloud, logs-apache.error-1.8.2
In Europe, we often use the ISO 8601 time format instead of the default US one (Tue Apr 11 11:37:47.559505 2023). The grok parser doesn't support that:
> P…
-
1. ISO 8601: https://www.w3.org/TR/xmlschema11-2/#duration
> duration is a datatype that represents durations of time. The concept of duration being captured is drawn from those of [[ISO 8601]](ht…
-
url: https://demo.coopcycle.org/register/confirmed?_business=1
GIF
![makingbusinessaccount](https://github.com/user-attachments/assets/9b1bc245-2961-4398-821b-9e99b5ce5a4f)
last page, the organiz…
-
### Please confirm the following:
- [X] I've checked [the current issues](https://github.com/Ivy-Apps/ivy-wallet/issues) for duplicate issues.
- [X] I've requested a single (only one) feature/change …
-
### Problem to solve
I want to uniform the date format to "YYYY-MM-DD" (ISO 8601 format) to avoid user mistakes.
(current version is: mm/dd/yyyy, which is a confusing date format)
### Proposed s…
-
I think it would be wise to use the international standardized date format, [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601). Droid-ify currently uses the traditional US date format.
| Format | N…
-
Here are an example that accepts 6 timestamp string that are all invalid according to ISO 8601:
```
from dateutil.parser import isoparse
for i in (
"2024-01-17T15:21:00-0800",
"2024-01-17T152…
-
Using ISO 8601 would prevent confusion between US/rest of world date formatting when using the `xx/xx/xxxx` format. And you could still use your nice fuzzy matching.
As usual, XKCD speaks the truth:
…
-
### Is your feature request related to a problem?
As a human, looking at users pillars it is hard to see when they expire.
### Describe the solution you'd like
Instead of this:
```
…
snago updated
4 years ago
-
```
DateParser doesn't handle all allowable ISO 8601 dateTime formats.
E.g. a parse exception is thrown when attempting to parse a valid ISO8601
dateTime such as '2009-11-23T13:29:24.604-05:00'.
See…