https://bugs.kde.org/show_bug.cgi?id=466795
--- Comment #1 from b...@mogwai.be --- Looking at the code I wouldn't expect this to happen since the remote episode actions are retrieved from the server before the local ones are uploaded. (This is needed anyway because we first need to solve any conflicts before sending the new action updates to the server.) Only the retrieved remote actions that are not superseded by a newer local one are then applied locally. So I would expect that a jump can only happen by picking up remote actions that have been uploaded on a previous sync, not the current one. The only way I can think of this happening would be if the clocks of the server and the client are not synced, or one or both have an incorrect timezone set. All internal timestamps are relative to UTC, but the conversion might be wrong if Kasts gets a wrong local timezone. If any of those conditions would happen, then Kasts might get confused and might apply actions in the correct order/precedence. -- You are receiving this mail because: You are watching all bug changes.
