Proget 2024.37 (Build 4) issues (tags and counters)

phopkins_6694

Just upgraded from way back on 5.x.x up to 2024.37.4 using docker. Also MSQL2017 to 2019 (docker) Couple of issues I cant figure out.

Steps I followed were

upgrade docker first to get all the new support for latest compose file
upgrade MSQL2019 first, then let it do it's own upgrade thing and 5.x.x did it's thing
upgrade to latest proget 2024.37.4 image, upgrade went well for the most part

Problems I now have

TAGS are no longer being displayed from our nuspec files. This is a choco feed and tags used to work really well for categorising, sorting, searching etc.
Download count for packages, this one seemed fine post DB upgrade so it was in the proget upgrade it went wrong. Download count is about 1/4 of what it was for packages.

Anyone seen this got any suggestions?

The TAGS are the most important, I can probably fudge the download count in SQL
Cheers,
Pete

stevedennis

Hi @phopkins_6694 ,

The "missing tags" is a regression from ProGet 2024.28 (PG-2911); it is a UI display issue and it's already been fixed in ProGet 2025.

Not sure about download counts, but there were some display changes in ProGet 2022 as well -- I think what you're seeing is the difference between "total downloads for all versions of the package" versus "downloads for this version".

Thanks,
Steve

phopkins_6694

Thanks @stevedennis , I'll have a poke at 2025 and see if it's good to move to. It does appear to be visual as we can search for tags via choco API etc, but not via the GUI search which I would have assumed called the API.

Yeah the total downloads is the "Downloads" column on the main page for each feed. So it would be a sum of all packages downloaded AFAIK. It's not super critical but is a good metric for us

phopkins_6694

Still no tags in Version 2025.3 (Build 9), and cant be searched for in UI
Trying a reindex for what it's worth

phopkins_6694

Update: Re-index did not correct the issue

stevedennis

Hi @phopkins_6694,

If you've upgraded, then the tags should now be displayed on the Metadata tab of the package.

When doing a search in the ProGet UI for NuGet (and Choco/PowerShell) packages, the Name, Description, and Tags are considered. However, the ordering may not be what you expect, especially if your tags are common words common in many names/descriptions.

Thanks,
Steve

phopkins_6694

@stevedennis Yep the metadata is definitely there, and searchable via choco CMD but not via the proget Search Box.
Here is an interesting thing though which might give you some clue as to what is going on...

If I have a local connector FEED_B going into that FEED_A I search for metadata and that works in the proget UI. So the connected FEED_B works through FEED_A, but then when I go to FEED_B direct and UI search it exhibits the same bug.

Hope that helps

stevedennis

Hi @phopkins_6694,

I'm afraid not; the Chocolatey client and ProGet UI perform different search functions so there's not much we do with that information.

If you can provide a very specific reproduction case, we can investigate:

Create a new Feed
Upload a package
Search the package in the ProGet UI

If you share the nuspec of the package you uploaded and your search terms, we can try to reproduce the case and see if we can reproduce. Then we can explain or fix the behavior.

Thanks,
Steve

phopkins_6694

@stevedennis will try and do before end of week, would any logs help as well?

stevedennis

Hi @phopkins_6694 ,

Probably not - the search in Chocolatey and ProGet UI will be different, and that's not something reasonably addressable. So let's start the issues you're having with ProGet UI search.

Thanks,
Steve

phopkins_6694

@stevedennis OK I made a test feed, used one of our existing packages and it fails to search. I also made a sanitised dummy package and it also fails. Looks like I cant attach files here so if you want I can email them, otherwise here is the code snippet for the dummy nuspec. Could not search for testX tags. Created with choco pack
Chocolatey v2.4.3

<?xml version="1.0"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
  <metadata>
    <id>test</id>
    <version>0.1</version>
    <authors>me@me.com</authors>
    <description>test nuspec</description>
    <tags>test1 test2 test3 test4</tags>
    <dependencies>
    </dependencies>
  </metadata>
</package>

phopkins_6694

Also I set up a connector on this TEST_FEED, absorbed into a new TEST_FEED2 and it exhibits that behaviour where I can search for tags in the TEST_FEED2 with proxy. Both a re choco feeds

stevedennis

@phopkins_6694 perfect, just what I was looking for

I was able to reproduce this - searches via the NuGet API (which connectors use) will consider tags, while local searches seem to only be looking at names.

I'm not sure how long this has been the case, but we'll try to get it fixed soon. Unfortunately it's not a trivial fix, hopefully we'll do it via PG-3046, likely in the July 18 maintenance release.

Thanks,
Steve

phopkins_6694

@stevedennis Nice one, thanks for all your help