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.

Sign up for GitHub

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

Jump to bottom

/subjects/queued endpoint is scrambling subject locations #2293

Closed
eatyourgreens opened this issue Apr 4, 2017 · 2 comments · Fixed by #2294
Closed

/subjects/queued endpoint is scrambling subject locations #2293

eatyourgreens opened this issue Apr 4, 2017 · 2 comments · Fixed by #2294
Assignees
@marten
Labels
bug

Comments

@eatyourgreens
Copy link
Contributor

Subject locations should match the order specified when the subject was created.

zooniverse/Panoptes-Front-End#3577 shows that this is fine for subjects requested by ID from the /subjects endpoint, but the array order is not being preserved for subjects requested from /subjects/queued.
@camallen camallen mentioned this issue Apr 5, 2017
Merged
4 tasks
@eatyourgreens eatyourgreens mentioned this issue Apr 5, 2017
Closed
@marten
Copy link
Contributor

marten commented Apr 5, 2017

I've done some minor digging. Looks like SubjectSelectorSerializer.page({}, Subject.where(id: 6532831)).to_json exhibits this issue. But not SubjectSelectorSerializer.resource({}, Subject.where(id: 6532831)).to_json.

@marten marten self-assigned this Apr 5, 2017
@camallen
Copy link
Contributor

camallen commented Apr 5, 2017

@marten i've got a PR up to solve this, #2294

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marten marten

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

sort location metadata index as ints not strings camallen/Panoptes
3 participants
@marten @eatyourgreens @camallen