dotnet-public mirror has all packages as listed despite the fact that they're unlisted on nuget.org

[nkolev92]

https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json is supposed to be faithful mirror of https://api.nuget.org/v3/index.json, but only packages used within our builds.

Take NuGet.Commands for example.
https://www.nuget.org/packages/NuGet.Commands

NuGet.org - https://api.nuget.org/v3/registration5-gz-semver2/nuget.commands/index.json. Many packages exist, some such as 3.2.0 are unlisted.

dotnet-public - https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/45bacae2-5efb-47c8-91e5-8ec20c22b4f8/nuget/v3/registrations2-semver2/nuget.commands/index.json - Every single package version is listed.

I imagine there's 2 challenges here.

1. Mirroring new packages. When the packages are mirrored and all their versions, their listedness is not perfectly matched.
2. Maintaining the listed status to match nuget.org. This is much costlier and I'd argue less important.

This discrepancy can lead to confusion about which exact versions to use.

Inspired by https://developercommunity.visualstudio.com/t/Nuget-Package-change-from-date-based-Ver/11139012

[mmitche]

@nkolev92 What is the behavior for CFS in this case? If a package was ingested from upstream nuget.org, and then unlisted on nuget.org, what happens?

[nkolev92]

Not sure whether there's anything specifically configured for CFS, but in talking to artifacts folks upstreaming snapshots the listedness status at the beginning and then every new ingested package is listed.

[mmitche]

dotnet-public should, as of earlier this year, have the same behavior.

[nkolev92]

Many of the packages I inspected have all their versions as listed. I think it's worth considering whether those can be fixed.