Conda feed not generating repodata.json for win-64 subdir

e.rotteveel_1850

First of all, @atripp : the constrains (i.e. optional dependencies) appears to be working. Thank you and your team! We're now trying to setup conda feeds with the 2023 version of ProGet and we can see the conda feed features improved!

However, the conda feed breaks down after uploading some packages. I cannot really find out what triggers the problem exactly, but I uploaded some example packages here:

https://nextcloud.marin.nl/index.php/s/7zBHSDx8QYLCzfJ

When I create a new, empty conda feed, the repodata.json works fine. I can go to one of:

And they look fine. Of course there are no packages yet.

If I upload the hello-inedo-triple package from my examples (via the manual upload in the WebGUI), the second link (noarch repodata.json) still works. But if I upload proget-package-2023.8.0-1.tar.bz2, the win-64 repodata.json link responds with:

Object reference not set to an instance of an object.

Meanwhile, the channeldata.json (https://my.proget.url/conda/my-conda-feed/channeldata.json) works perfectly fine.

I hope you can look into this, thanks!

atripp

Hi @e-rotteveel_1850 ,

Thanks for sharing the packages for this (and that other CONDA issue); my wild-guess is that it's related to your package metadata. But we'll use your packages, attach a debugger and find out :)

Please give us a few days to investigate/resolve this, and hopefully it'll be a very easy fix.

e.rotteveel_1850

Thanks for the effort again!

I just tried with one of the numpy packages on the main conda channel:
https://repo.anaconda.com/pkgs/main/win-64/numpy-1.23.5-py39h6917f2d_1.tar.bz2

And I get the same problem with the win-64/repodata.json URL.

It went okay with one of our own packages though (but not with another). But even after comparing the metadata for both packages in detail I was not able to find problematic data or characters (none that I could think of).

Looking forward to the fix!

gdivis

Hi @e-rotteveel_1850

Thanks again for the packages and detailed repro steps. I was able to reproduce this and we'll have a fix (PG-2445) in this Friday's release (v2023.14). It appears to have been a regression introduced when we added support for parsing package constrains information from connectors.

-Greg

e.rotteveel_1850

Sorry for my late reply, but we have since installed version 2023.16 and repodata.json works perfectly fine now! Thanks for including this in your updates.