Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
ProGet 2023 - Packages not listed on local NuGet feeds
-
When listing packages on a local NuGet feed it will not show the number of packages selected to show.
As we're evaluating this we upgraded from 2022.x (where everything looked ok) to 2023.1 to test the new release.
First thought was "it's just a bad upgrade" so we did a new installation and uploaded all packages again but to the same result.
Each package have a few versions (~40) and none are set to unlisted or depricated.
It seems like the internal counter includes individual package versions when counting and from that result shows the latest of each package.Packages are available if doing a specific search, but still only showing one in the list.
To be able to see a second package in the list we have to set the Count to 100. Setting Count to 500 show 7 packages,
so this makes me think it includes all versions when counting and not only the latest which should be shown in the list.
What am I missing? Is there some config setting I need to set?We're running ProGet 2023.2 (Build 12) Free Edition.
-
Hi @magnus-wiksell_6950 ,
I think you identified the underlying issue...
It seems like the internal counter includes individual package versions when counting and from that result shows the latest of each package.
... it's not clear to me, but are you saying that this is happening only in ProGet 2023? And that this wasn't a problem in ProGet 2022?
We just released a few days ago, and since there were some major changes to the underlying indexing system (i.e. database), there will be a few UI regressions here and there.
FYI: I haven't investigated this yet, but the "Feed View" is surprisingly complicated under the hood, since it does all sorts of aggregation with connectors, and combining local and remote packages into one view. Obviously this shouldn't be happening, but you can get a much simpler view under the "Packages" tab on the top navigation.
-
Yes, it’s working in 2022. I still running that version on my dev machine.
-
I believe this has already been fixed as part of PG-2343 in v2023.3, which we are releasing today. In addition to being slow, the NuGet queries responsible for handling latest versions could return a lot more results than necessary. It didn't lead to incorrect behavior (except with counts) as we still validate and filter results in the frontend, but did cause problems like this.
