Error: Cannot parse 2022-12-02+06:47:45.300389 00:00 as a valid ISO-8601 date #71
Comments
|
Also getting this error, and not seeing bolus doses on NS. |
|
I'm getting this same error with v0.8.7 (pip install in google cloud VM). I then experimented in another VM instance with a pipenv install. I confirmed I got the same error with v0.8.7 with only the BOLUS feature specified. Then I checked out the v0.8.5 tag and I still got the same error. Then I checked out the 0.8.3 tag and I do NOT get any errors and I got bolus data in nightscout. So this appears to be related to a change between v0.8.3 and v0.8.5. A temporary workaround for those running into problems may be to revert back to v0.8.3 for now (assuming the issues resolved in v0.8.5 and v0.8.7 weren't causing you problems before). |
I suppose this fixed jwoglom#71 for me.
|
Changing this resolved it for me -- I'm not opening a PR because I don't know the cases in which we want the T-substitution or what the original purpose was. However the workaround that works for me is on line 82 of |
|
All -- attempted to work around this case, please take a look with the latest version (v0.8.8). Unfortunately different (older?) versions of Nightscout seem to be inconsistent with timestamp format -- e.g., a version I tested with returns no results when entering an invalid timestamp instead of a 5xx error. |
|
Thank you! I'll pull your branch and give it a shot. |
|
Is v0.8.8 available now? As when I try to install using pip3 I get the error "No matching distribution found" |
|
@diabetesman I just manually ran the workflow action to push the new release to pypi; check to see that it's available in a few minutes |
|
@TimValishev @LvnInLevis @kswick @jlecount @diabetesman Just want to confirm that everything is working okay for you all with the latest build. If so, I will close this issue. |
|
Thanks so much, @TimValishev - I'll give it a shot today... |
|
Yep, this is working great -- thanks again! |
|
Hi, I tested it with v0.8.8 and it was working and I just upgraded to
v0.8.10 and it's still working. Thanks for fixing it.
Thanks
…On Sat 7 Jan 2023, 06:02 James Woglom, ***@***.***> wrote:
@TimValishev <https://github.com/TimValishev> @LvnInLevis
<https://github.com/LvnInLevis> @kswick <https://github.com/kswick>
@jlecount <https://github.com/jlecount> @diabetesman
<https://github.com/diabetesman> Just want to confirm that everything is
working okay for you all with the latest build. If so, I will close this
issue.
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANMM2J3KU6KTHIVZXJJDBGDWREBGBANCNFSM6AAAAAASSS3VGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Great, I will close the issue. |
|
Hi all, I have 0.9.3 installed from pip on OS X and I'm running into this issue. Is there something I should do on the nightscout side to fix it? |
|
I had version 0.7.x, which was working fine for quite a while, but lately got spotty. I updated tconnectsync and now I too have this same issue on 0.9.3, installed via pip3.9 on an openSUSE machine. My nightscout version is 14.2.5. Same error if I downgrade to 0.8.10, or 0.8.7. Updated NS to 14.2.6 and still have the same issue. I've tried version 0.8.1, 0.8.5, 0.8.3. None are now working. Error is: "Error: Cannot parse 2023-05-28+15:10:20.171680 00:00 as a valid ISO-8601 date" @jwoglom is there anything I can provide to assist in sorting this out? |
|
I am also having an issue. Latest version of NS & tconnectsync. |
|
@clegoues @vincepf @ramboozer can you give a full traceback of the error and also run with --check-login? You can reply here or email this to tconnectsync at wogloms.net |
|
@jwoglom Thank you for the reply and all of your tremendous work on this. It's really a lifesaver for our family. I apologize; the last time I tried it a few days ago it had the error mentioned and would not upload to Nightscout; as of 6/20/23 22:15 I ran it via a cron job, the STDERR log it shows the same error in the output of tconnectsync, but now appears to be working properly. Our nightscout data is now current. Perhaps it was a t:connect site issue? |
|
@jwoglom |
|
Appears that TSlim app on my phone auto logged me out. I logged back in and all the errors went away. I imagine the data wasn't being populated. |
|
-- tconnectsync 0.9.6 via docker-compose on unraid and nightscout version 15.0.2, also docker-compose on unraid. @jwoglom I'm now seeing this error. It appears to be a Nightscout issue? The GET request is asking for A quick Google search also shows that is not a valid ISO-8601 date. tconnectsync appears to be able to POST data alright since Nightscout is returning 200's to that part in the logs. Similar to ramboozer, last week-ish I was auto logged out as well but now I'm getting this error. I logged into t:connect and it appears to have up-to-date data right now. As does the Android app. I've prepared a log file if that would be helpful. Edit 4 hours later: well I just noticed the data appeared from today. So something fixed itself. |
|
@starbuck93 I think the root cause of this problem is that some versions of Nightscout are liberal in what timestamp format they accept from clients, and some are not. I haven't completely tracked this down. Personally, I'm still running a several years old version of Nightscout which doesn't help matters in my testing. However, tconnectsync should now detect this error and try again with a modified timestamp format if it detects the problem having occurred. So that might be why you see this problem in the log but the data eventually reconciled into Nightscout. Let me know if it stops working again. |
Man, thank you for the fast reaction to the previous one! Here's what I see in 0.8.7 (my Nightscout version is 14.2.5):
<title>Error: Cannot parse 2022-12-02+06:47:45.300389 00:00 as a valid ISO-8601 date</title> <style>* { margin: 0; padding: 0; outline: 0; }body {
padding: 80px 100px;
font: 13px "Helvetica Neue", "Lucida Grande", "Arial";
background: #ECE9E9 -webkit-gradient(linear, 0% 0%, 0% 100%, from(#fff), to(#ECE9E9));
background: #ECE9E9 -moz-linear-gradient(top, #fff, #ECE9E9);
background-repeat: no-repeat;
color: #555;
-webkit-font-smoothing: antialiased;
}
h1, h2 {
font-size: 22px;
color: #343434;
}
h1 em, h2 em {
padding: 0 5px;
font-weight: normal;
}
h1 {
font-size: 60px;
}
h2 {
margin-top: 10px;
}
ul li {
list-style: none;
}
#stacktrace {
margin-left: 60px;
}
</style>
Connect
500 Error: Cannot parse 2022-12-02+06:47:45.300389 00:00 as a valid ISO-8601 date
The text was updated successfully, but these errors were encountered: