NullReferenceException at Inedo.ProGet.Feeds.NuGet.NuGetConnector.FindPackagesByIdAsync

[RobIII]

This is a continuation on this message. I'm not quite sure if closing the topic was the best option, but OK.

Is it possible to share access to your GitLab repository?

I'm afraid I won't be able to 'open up' our GitLab instance to the internet, corporate won't be too happy about that I'm afraid ;-)

That's the easiest thing of course, but you say "on-prem" so maybe not so easy.

Agreed, that would be easiest. But, indeed, not so easy.

As an alternative, can you create a simple reproduction case using a public GitLab repository? This way, we can plug ProGet into it, attach a debugger, and figure out what's going on.

I'm not sure how I would go about that; we have dozens of packages in our repository, it may be only one specific package that causes the issue?

I'll see if I can intercept the ProGet traffic and dump that and reconstruct the requested JSON's to some files or something. Maybe that will help? Let me see what I can do to get you the most information to (try to) repro the issue. Crap, it's SSL ofcourse... Hmm... let me think this through...

Edit: Ok. Best I can come up with currently is I dump the searchresults for the queries "a", "e", "i", "o" and "u" , all with a &take=1000, which should return all packages in any of the 5 files. Maybe you can find an issue that way?

I'll send the JSON files to support@inedo.com as previously. Let's see where that takes us and go from there?

Please not I will be on holiday for the next two weeks so it may take a while before I reply.

[atripp]

Thanks for sending those over @RobIII

At first I want to confirm, are you using the "V3" API endpoint in ProGet, for your VS2019 configuration? If not, please do that, since VS treats those APIs differently.

Otherwise, there's nothing off about the index files... the most likely scenario is that there is a problematic "translation" between VS2019's API call to ProGet, and ProGet's API call to GitLab. There are more than just those index files that are used.

It's most likely a bug on GitLab's end, in that they're doing something against the spec that just "happens to work" in VS2019. We struggled with a very similar bug with GitHub, but their timeline to investigate/fix it was crazy, so we just did a workaround (see PG-1932) and have it mostly working.

Ultimately, the customer decided not to use GitHub in this manner, because the workflow (outside of the API) was painful and GitHub is buggy they said. So there's that. They just publish packages to ProGet directly instead. You may find this workflow better as well.

Anyways... if you're already using the v3 api endpoint in ProGet, we will need to get this reproduced so we can attach a debugger and find the problem.

I understand it's not feasible to provide access... maybe it won't be so bad to set-up a reproduction case with a public repository? We don't know how to use GitLab's packages features, so if you can help set that up, we can attach a debugger and get it tested.

Thanks