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
When I log a flight that starts before 10am AEST (00:00 GMT) and the flight spans 00:00 GMT, the live tracking page doesn't request the track with the correct last_update value.
Attached example shows 86400 (seconds in day) being subtracted from the actual last_update value before it is used in the request to the server. There's a continuous flip flop between the actual and the subtracted last_update value after that.
The result is that large amount of data is unnecessarily being sent to the client and also the barogram display is corrupted by this.
My user id is 8746 and data is logged using the iOS FlySkyHy app
The text was updated successfully, but these errors were encountered:
When I log a flight that starts before 10am AEST (00:00 GMT) and the flight spans 00:00 GMT, the live tracking page doesn't request the track with the correct last_update value.
Attached example shows 86400 (seconds in day) being subtracted from the actual last_update value before it is used in the request to the server. There's a continuous flip flop between the actual and the subtracted last_update value after that.
The result is that large amount of data is unnecessarily being sent to the client and also the barogram display is corrupted by this.
My user id is 8746 and data is logged using the iOS FlySkyHy app
The text was updated successfully, but these errors were encountered: