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

extensions/live not a "fixed" order #539

Closed
BarryCarlyon opened this issue Dec 16, 2021 · 3 comments
Closed

extensions/live not a "fixed" order #539

BarryCarlyon opened this issue Dec 16, 2021 · 3 comments
Labels
product: api API endpoints in the "helix" namespace ticketed Has been given an internal tracking ticket

Comments

@BarryCarlyon
Copy link
Contributor

BarryCarlyon commented Dec 16, 2021 •
edited

Brief description

In an extension of the issue in #524

How to reproduce

If you load live activated channels.
Then load it again

The order of results is different.

This is further seen by setting ?first=2 and just loading again and againm

Expected behavior

The order ot be consistent
@BarryCarlyon BarryCarlyon added the product: api API endpoints in the "helix" namespace label Dec 16, 2021
@BarryCarlyon BarryCarlyon mentioned this issue Dec 16, 2021
Closed
@iProdigy iProdigy mentioned this issue Feb 10, 2022
Merged
2 tasks
@jbulava
Copy link
Member

jbulava commented Feb 10, 2022

Created a ticket related to #540 to investigate.
HLX-2299

@jbulava jbulava added the ticketed Has been given an internal tracking ticket label Feb 10, 2022
@jbulava
Copy link
Member

jbulava commented Jun 6, 2022

The team has deployed the fix for this today.

@jbulava jbulava closed this as completed Jun 6, 2022
@BarryCarlyon
Copy link
Contributor Author

Looks good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
product: api API endpoints in the "helix" namespace ticketed Has been given an internal tracking ticket
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BarryCarlyon @jbulava