[
https://issues.apache.org/jira/browse/AIRAVATA-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647457#comment-17647457
]
ASF subversion and git services commented on AIRAVATA-3677:
-----------------------------------------------------------
Commit d56604c77cb25f38ff3ad5a46bb22a74fb21c42b in airavata-django-portal's
branch
refs/heads/dependabot/npm_and_yarn/django_airavata/apps/dataparsers/moment-2.29.4
from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=d56604c7 ]
AIRAVATA-3677 For the sake of consistency, always include microseconds in
ISO8601 dates
> 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
> Priority: Major
>
> 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)
