You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Marcus Christie (Jira)" <ji...@apache.org> on 2022/12/05 20:44:00 UTC
[jira] [Created] (AIRAVATA-3677) time data '2022-01-11T21:20:38Z' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'
Marcus Christie created AIRAVATA-3677:
-----------------------------------------
Summary: time data '2022-01-11T21:20:38Z' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'
Key: AIRAVATA-3677
URL: https://issues.apache.org/jira/browse/AIRAVATA-3677
Project: Airavata
Issue Type: Bug
Components: Django Portal
Reporter: Marcus Christie
Assignee: Marcus Christie
The Django REST Framework serializes dates to the ISO-8601 format, but it doesn't always include microseconds. This is because it relies on [datetime.isoformat|https://docs.python.org/3/library/datetime.html#datetime.datetime.isoformat] which only includes microseconds if microseconds are not 0. However, this behavior, that it sometimes and sometimes does not include microseconds, makes it challenging to parse the returned values.
For this task, I'll set the [DATETIME_FORMAT|https://www.django-rest-framework.org/api-guide/settings/#datetime_format] settings in Django REST Framework to force always include microseconds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)