Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISO8601 time parser bug with different resolutions with range #120

Open
jbfaden opened this issue Dec 5, 2024 · 3 comments
Open

ISO8601 time parser bug with different resolutions with range #120

jbfaden opened this issue Dec 5, 2024 · 3 comments

Comments

@jbfaden
Copy link
Member

jbfaden commented Dec 5, 2024

In Autoplot, the bug is demoed with:

print DatumRangeUtil.parseISO8601Range('2016-05-20T07:46.19.400/07:46:19.8')

Sadie reported this.

@jbfaden
Copy link
Member Author

jbfaden commented Dec 6, 2024

This is handled when the differences is in the length of subseconds.

@jbfaden
Copy link
Member Author

jbfaden commented Dec 6, 2024

The following script should run without errors:

print DatumRangeUtil.parseISO8601Range('2016-05-20T07:46.19.400/07:46:19.8')
print datumRange('2016-05-20T07:46:19.400 to 07:46:19.8')
# print datumRange('2016-05-20T07:46.19.400 to 07:46:19.8')  # make sure error is clear about : vs .
print DatumRangeUtil.parseISO8601Range('2016-05-20T07:46/07:46:30')  # difference in minute/seconds resolution
print DatumRangeUtil.parseISO8601Range('2016-05-20T02/07')  # Hours has never worked, but this is a similar problem (tack on ":00" and then do as before)

@jbfaden
Copy link
Member Author

jbfaden commented Dec 6, 2024

#119 was a lost ticket. I've closed it and this one should be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant