Incorrect timestamps when returning latest items #1
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Chewing_Bever/otter#1
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
The Gpodder API returns a timestamp value for certain routes indicating the value that should be used as the
since
parameter for the next request to the endpoint.The current implementation always returns the timestamp of the latest element incremented by 1. This isn't correct if the latest returned element is in the past. The timestamp should reflect that no more elements are present between the last element's timestamp and the current UNIX timestamp.
To fix this, the API should instead return the current UNIX timestamp if it's returning the latest elements.