Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with API ordering that results in winner_count/seats_contested not updating #2132

Open
VirginiaDooley opened this issue May 14, 2024 · 0 comments
Assignees

Comments

@VirginiaDooley
Copy link
Contributor

Ref https://app.asana.com/0/1204880927741389/1207254815979876/f

There is some kind of non-deterministic ordering bug going on here. If I call
https://elections.democracyclub.org.uk/api/elections.json?future=1&limit=100&offset=0 and
http://elections.democracyclub.org.uk/api/elections.json?future=1&limit=100&offset=100
those two pages of results shouldn't contain any duplicates, but local.north-northamptonshire.desborough.by.2024-04-04 sometimes appears in both pages (interestingly, if I call http://elections.democracyclub.org.uk/api/elections.json?future=1&limit=100&offset=100 a few times, sometimes that election is in it and sometimes it isn't) (edited)

Could this be some version of #2038 back again?

Possible solution: Add the election_id to the sort_by, following group_type

@VirginiaDooley VirginiaDooley self-assigned this May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant