Collections can have mismatched total entries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
New
|
Undecided
|
Unassigned |
Bug Description
In at least one case, the Launchpad API is returning the following JSON:
{"total_size": 1, "start": 0, "entries": [], "resource_
Obviously the total_size value of 1 does not match the number of entries available, which is zero.
I believe that this case is due to the OAuth credentials having read access to the gitref, but not to the merge proposal that the collection contains. So in one sense the total_size is correct (there is one merge proposal), but it is invisible to this account.
This makes it difficult for code to rely on the total_size value when fetching entries in the collection. If this is considered to be working-as-intended from a code/API perspective, then it is likely a documentation bug as there does not appear to be any description of this behaviour (or how it should be handled) here:
https:/