-
Notifications
You must be signed in to change notification settings - Fork 68
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
500 - Error: Cannot parse 2024-06-13+08:49:09.971622 00:00 as a valid ISO-8601 date #93
Comments
I think this is a Nightscout time formatting bug, not an issue on Tandem's end. Tconnectsync has logic to try two different timestamp formats when querying Nightscout to work around this, so I think this warning can be ignored in your case. |
the date/time returned from Nightscout above in the error message is indeed not a valid ISO-8601 datetime
according to the spec, the date/time separator should be a
are we passing the correct date and Nightscout isn't handling it? or are we passing the invalid date and Nightscout is spitting it back verbatim? |
Older versions of Nightscout appear to accept writes via the API into Mongo with invalid-formatted dates. (I don't want to throw any blame here, but it might have been an xDrip+ bug?) This means that in some cases the invalid iso-8601 formatted date needs to be sent in order to properly filter dates. Currently, tconnectsync works around this bug by attempting both the "correct" and "incorrect" formats in sequence, and trying the other if such a http 500 occurs. |
i got this warning, twice, and started to dig in since the error message is i was able to reproduce the empty list with the offending datetime multiple times but eventually nightscout returned the expected result and i could no longer reproduce 🤔 |
It looks like Tandem's API might have changed recently (7.17.2.3) and broken things?
I haven't dug deeper into this yet, but it looks like perhaps the date stamps passed to their server need to be adjusted a bit.
The text was updated successfully, but these errors were encountered: