Not all pushed packages are available
See original GitHub issueHi Loïc,
I’m using BaGet for a month and I’ve pushed and used many packages without encounter any problem, but today I’ve pushed the 9th package and it is not listed in Visual Studio or in the server web. I’ve removed a package, and the last package I pushed appeared just for a while, after it has disapeared again.
In the server side I can see this warning:
warn: Microsoft.EntityFrameworkCore.Query[20500]
The LINQ expression 'GroupBy([p].Id, [p])' could not be translated and will be evaluated locally.
System configuration LXC over Ubuntu 18.04 BaGet commit ed0e62d3bdf29aecc4edbfb1f2a48e140769165c Hosting environment: Development (how to change it?)
Thank you for your help and the good job.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Some nuget packages are not getting pushed to the gitlab ...
I am pushing nuget packages to a test repo in gitlabs. It says the packages were successfully pushed but they don't show up...
Read more >NuGet package manager cannot find recently pushed ...
NuGet package manager cannot find recently pushed packages (for a period of time) ... But still the new package version is not found....
Read more >Troubleshoot missing packages - Deployments
Make sure the correct package is pushed to the built-in repository and try the deployment again.
Read more >nuget package manager don't show installed ...
I have a project builded in vs2019. Update from vs2019 to vs2022. Open project -> nuget package manager -> installed panel Not found...
Read more >Troubleshooting Installed Packages - NuGet
When a package is not available locally, either in the global-packages folder, a fallback folder, or a local file source, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Don’t we want the skip and take to occur after the grouping? I think what’s currently happening is the total list of ungrouped packages are being limited/paged, and then the limited list is being grouped. For example, if you had a single package with 20+ versions, the default query would skip 0 and take 20, which would only be grabbing the first 20 versions of the package, and the group that single package.
I think
should be:
Now we’re getting packages grouped by package id, and then paging on those results.
This should be fixed by https://github.com/loic-sharma/BaGet/commit/ef5970904c62b7c9cf712d8c4a64151774155c6b#diff-86483935118f023a4828d37181ae9416. Feel free to open a new issue if anything else comes up!