You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to my reading of the spec and the output of Python's rfc3339-validator package, "2020-05-07 16:51:21 +0000 UTC" is not valid - there should be a 'T' between date and time, there should not be a space before offset, the offset should be formatted hh:mm and there should not be a timezone on the end.
I think equivalent compliant timestamps would be 2020-05-07T16:51:21+00:00 and 2020-05-07T16:51:21Z
Checklist:
What happened:
Workflow parameter
workflow.creationTimestamp
did not output a timestamp in RFC3339 compliant format.What you expected to happen:
Documentation states it should output a timestamp compliant with RFC3339
How to reproduce it (as minimally and precisely as possible):
Output:
Anything else we need to know?:
According to my reading of the spec and the output of Python's rfc3339-validator package, "2020-05-07 16:51:21 +0000 UTC" is not valid - there should be a 'T' between date and time, there should not be a space before offset, the offset should be formatted hh:mm and there should not be a timezone on the end.
I think equivalent compliant timestamps would be
2020-05-07T16:51:21+00:00
and2020-05-07T16:51:21Z
Environment:
Other debugging information (if applicable):
Logs
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: