Open pharr117 opened 11 months ago
The error is here:
This means that the RPC endpoint is giving back a date that is not ISO format. I will need to figure out which network is throwing the error and what date format it is returning.
This actually has to do with the time returned by the RPC endpoint having a variable number of milliseconds.
We had anticipated this in our date parser function here:
However, the regex only looks for times that have MORE than 6 levels of precision, and the error is indicating 5 levels of precision: 2023-10-19T17:43:49.9951+00:00
.
I will try to just turn the regex into a string split + add/remove levels of precision to get to the required 6 levels of precision for ISO.
One of the update loop iterations is failing on a bad date string:
We need to catch the error and/or parse the string differently depending on the issue.