You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I think the TableListener C code has a timestamp bug, because the timestamp for each update is not set to milliseconds, only showing the seconds.
For example I currently get the following timestamps.
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
Should be something like this.
2019-06-24 19:13:43.022
2019-06-24 19:13:43.053
2019-06-24 19:13:43.068
2019-06-24 19:13:43.070
This is a fairly critical bug because there is no way to eliminate 'out of order' ticks/updates, would appreciate if someone could look into it ASAP.
Cheers
James
The text was updated successfully, but these errors were encountered:
Hi James. I have the exact same issue. How did you get around fixing it? I have tried Real login credentials to see if that would fix it as mentioned in some blogs but no luck on that front
Hi,
I think the TableListener C code has a timestamp bug, because the timestamp for each update is not set to milliseconds, only showing the seconds.
For example I currently get the following timestamps.
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
Should be something like this.
2019-06-24 19:13:43.022
2019-06-24 19:13:43.053
2019-06-24 19:13:43.068
2019-06-24 19:13:43.070
This is a fairly critical bug because there is no way to eliminate 'out of order' ticks/updates, would appreciate if someone could look into it ASAP.
Cheers
James
The text was updated successfully, but these errors were encountered: