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

Nuget backend returns incorrect number of packages #2895

Closed
yishaigalatzer opened this issue Feb 18, 2016 · 3 comments
Closed

Nuget backend returns incorrect number of packages #2895

yishaigalatzer opened this issue Feb 18, 2016 · 3 comments

Comments

@yishaigalatzer
Copy link

from @jianyunt

Recently, when we use nuget API v2 and ODATA syntax to query the server, we get back the wrong number of packages. Specifically, the URL
https://www.nuget.org/api/v2/Search()?$filter=IsLatestVersion&searchTerm=''&targetFramework=''&includePrerelease=false&$skip=320&$top=40 returns 39 packages instead of 40. This used to work before but now it is broken (we are not sure when this happened). Is this a known issue?

@yishaigalatzer
Copy link
Author

We recently made a change to the gallery so this could be a regression.

At the same time, this is a very costly query, and we much appreciate if you stop using these if possible, and use an alternate V3 protocol for your queries (that relies directly on storage rather than database access).

If you can specify what exactly you are looking for we will be glad to help

@maartenba
Copy link
Contributor

Fixed this regression - will be deployed next week.

@maartenba
Copy link
Contributor

Deployed.

jozefizso added a commit to goit/NuGetGallery that referenced this issue Feb 26, 2016
* deployment_2016_03: (37 commits)
  Fix NullReference in unit tests
  Check for duplicate dependencies when uploading package
  Fix indentation
  fix CA errors
  create support request when user submits authenticated contact form + refactoring
  Minor layout change on contact support page
  Adding ContactSupport form and associated services
  Fix broken unit test after client library update (the client now has this logic)
  ToFriendlyName() now supports "portable40" and "portable45" TFM
  Fix OData - Hijacked projection + order by
  Nuget backend returns incorrect number of packages NuGet#2895
  convert IEntitiesContext.SaveChanges into SaveChangesAsync
  Removing obsolete PackageStatistics code from the gallery
  Propagate correlation id from gallery to search service
  fix test
  removing the support request link from the generated support email for now
  when there are no issues yet, we can still show the manage admins link
  support request feature
  OData does not copy headers from the main request to the batch sub-request
  Suppress CA warning
  ...
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

2 participants