Open trevorcarlson opened 10 years ago
Will take a look soon, but I see some other column values are changing in the screenshot. What are those columns? The GPSd data is never modified - simply serialized so it can be sync'ed, and this isn't the dummy data in the mock.
Jeff
On Apr 3, 2014, at 7:58, trevorcarlson notifications@github.com wrote:
Recently, we've seen our first demonstrator (kpi-1) send data with all of the same fields to the server. The server (received) timestamp is incrementing, but all other data is exactly the same. It appears that there could be a bug in the client code.
[image: screen shot 2014-04-03 at 7 57 46 am]https://cloud.githubusercontent.com/assets/1049545/2602907/3537d366-bb27-11e3-9945-5a6ea7845258.png
— Reply to this email directly or view it on GitHubhttps://github.com/kinisi/kinisi-agent-nodejs/issues/2 .
The data that is changing is the time when the server receives the data. But, the GPS data itself appears to be the same. Weird, right?
On Apr 3, 2014, at 8:41 AM, Jeffrey Yang notifications@github.com wrote:
Will take a look soon, but I see some other column values are changing in the screenshot. What are those columns? The GPSd data is never modified - simply serialized so it can be sync'ed, and this isn't the dummy data in the mock.
Jeff
On Apr 3, 2014, at 7:58, trevorcarlson notifications@github.com wrote:
Recently, we've seen our first demonstrator (kpi-1) send data with all of the same fields to the server. The server (received) timestamp is incrementing, but all other data is exactly the same. It appears that there could be a bug in the client code.
[image: screen shot 2014-04-03 at 7 57 46 am]https://cloud.githubusercontent.com/assets/1049545/2602907/3537d366-bb27-11e3-9945-5a6ea7845258.png
— Reply to this email directly or view it on GitHubhttps://github.com/kinisi/kinisi-agent-nodejs/issues/2 . — Reply to this email directly or view it on GitHub.
Recently, we've seen our first demonstrator (kpi-1) send data with all of the same fields to the server. The server (received) timestamp is incrementing, but all other data is exactly the same. It appears that there could be a bug in the client code.