Pagination broken for Nuget packages

[pf-uvonceumer]

Select Topic Area

Bug

Body

It seems like the NuGet API of GitHub Packages ignores the pagination parameter &take=10 in the request.

Example request:

curl --location --request GET 'https://nuget.pkg.github.com/<owner>/query?take=10&skip=0' \
--header 'Authorization: Bearer SECRET'

will return the exact same result as

curl --location --request GET 'https://nuget.pkg.github.com/<owner>/query?take=10&skip=10' \
--header 'Authorization: Bearer SECRET'

This causes very irritating issues when

• browsing NuGet packages in Visual Studio (results are repeated after 50 entries!)
• trying to list all packages, but only getting the same 50 results

This is clearly a bug, because the standard NuGet from nuget.org works as expected:

curl --location --request GET 'https://azuresearch-usnc.nuget.org/query?take=10&skip=10'

returns the next 10 hits after

curl --location --request GET 'https://azuresearch-usnc.nuget.org/query?take=10&skip=0'

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[BrendenWalker]

Noticed the same issue here. We have a bit over 100 packages, if I skip=0 and take 10, then skip 10 and take 10 the same 7 results are returned. Also tried take=100 and was getting 69 results, not seeing a pattern there.

[pmandalka]

As far as I remember, it depends how many versions are in the packages and the take parameter seems to take only X versions - but also in a very unspecific order, so sometimes you get 10 version from package A and 90 version of package B even if package A has more then 10 versions.

[ws-markb]

We're also seeing rather odd behaviour. We have 91 packages in total, but the following command (which I would expect to always return 10 results) returns 8 results:

curl --location --request GET 'https://nuget.pkg.github.com/[OUR ORG NAME]/query?q=&take=10&skip=10'

It then returns the same 8 results, no matter what the skip parameter is changed to.

If I include the prerelease option (because we have a number of alpha/beta package versions), I get 9 results, but also always the same 9 when the skip parameter is changed.