fromdate doesn't support fractional seconds

[bryanlarsen]

Using jq-1.5 from https://github.com/stedolan/jq/releases/download/jq-1.5/jq-linux64

AFAIK, fractional seconds are valid ISO8601.

jq: error (at <stdin>:1180): date "2016-03-17T17:06:59.764Z" does not match format "%Y-%m-%dT%H:%M:%SZ"

I don't care about the milliseconds, perhaps some people do. That's a harder problem, since you output in an int. But for people who don't care, perhaps you can make a fromdate variant that drops the milliseconds.

The workaround for now for me is:

| sub(".[0-9]+Z$"; "Z") | fromdate

[mauvm]

Thanks for the workaround! This helps parsing Bunyan log records. I use a slightly altered regex to make sure it's a literal dot:

| sub("\\.[0-9]+Z$"; "Z") | fromdate

[phiresky]

This is especially annoying as JSON.stringify produces these strings (e.g. JSON.stringify({now: new Date()}) => {now: "2017-11-08T01:00:36.383Z"} which are annoying to parse with jq.

[DBarthe]

To parse iso8601 dates with timezone offset (#1053 ) and fractional seconds, this should work :

sub("\\.[0-9]+\\+"; "+") | strptime("%Y-%m-%dT%H:%M:%S%z")

[elyscape]

That'll only work with a positive timezone offset. An improved version that supports all offsets would be:

sub("(?<time>T[0-9:]+)(\\.\\d+)?(?<tz>Z|[+\\-]\\d{2}:?(\\d\\d)?)$"; .time + .tz) | strptime("%Y-%m-%dT%H:%M:%S%z")

It's a lot uglier, though.

[jahmad-fareportal]

That'll only work with a positive timezone offset. An improved version that supports all offsets would be:

sub("(?<time>T[0-9:]+)(\\.\\d+)?(?<tz>Z|[+\\-]\\d{2}:?(\\d\\d)?)$"; .time + .tz) | strptime("%Y-%m-%dT%H:%M:%S%z")

It's a lot uglier, though.

@elyscape That works the best !!

[n2N8Z]

@DBarthe @elyscape these regexes delete the fractional seconds, which doesn't address the problem reported in this issue. Using these modified timestamps in a sort_by will result in incorrect order.

[elyscape]

I mean yes, but it works around not being able to parse the date at all.

[mluis7]

Yet another workaround to convert an iso8601 date as "2021-08-11T00:49:38.359Z" to a Unix timestamp in milliseconds. For example, the startedDateTime value from a HAR file

 ((.startedDateTime[0:19] + "Z"|fromdateiso8601)*1000 + (.startedDateTime[20:23]|tonumber))

Result: 1628642978359

date -d "2021-08-11T00:49:38.359Z" '+%s'
1628642978

So: (1628642978 * 1000) + 359

[andrewpollock]

My use case is processing https://nvd.nist.gov/developers/vulnerabilities data in https://csrc.nist.gov/schema/nvd/api/2.0/cve_api_json_2.0.schema, which seems to be in RFC 3339 format, e.g.:

1988-10-01T04:00:00.000

[wader]

I posted a workaround in another issue that might be interesting #1409 (comment)