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

viceice

Today i got some proget errors from my github package connector:

System.NullReferenceException: Object reference not set to an instance of an object.
at Inedo.ProGet.Feeds.NuGet.NuGetConnector.FindPackagesByIdAsync(NuGetQueryOptions options, String id) in C:\InedoAgent\BuildMasterTemp\192.168.44.60\Temp\_E91433\Src\ProGetCoreEx\Feeds\NuGet\NuGetConnector.cs:line 296

My connector:

Using ProGet on Docker for Linux: Version 5.3.19 (Build 9)

proget.inedo.com/productimages/inedo/proget:5.3.19@sha256:03b64607a3c7be571bc37acec8965efa05723994678d8f99ecac6e45d7ae8c53

rhessinger

Hi @viceice,

This typically happens because the NuGet package metadata has an invalid format. Does this error happen for all packages or just one?

We run into similar issues when connecting to Azure DevOps registries because they do not always follow NuGet's API spec. Are you able to send over the package registration metadata for a package with the issue? The index.json may also help with this. If you do not feel comfortable submitting this via the forums, you can email it to support@inedo.com. Just please let me know when you send it so I know to look in that mailbox for it.

Thanks,
Rich

viceice

I'm not sure which package causes this issue, but the packages are all public, see https://github.com/orgs/visualon/packages

I'm pretty sure it was one of those packages:

You need a github account to use the feed above, because github requires you to login.
So i think you should be able to reproduce the issue.

rhessinger

Hi @viceice,

I took a look at this and it looks like the issue is that the GitHub repository is not returning the published date. I have put a fix in, PG-1871, which will release in ProGet 5.3.21.

Thanks,
Rich

RobIII

I'm experiencing the same (or something very similar:

This started happening quite recently but I don't have an exact date. We were running ProGet 5.3.31 if I'm not mistaken and upgraded to the current 5.3.35. We're using a connector to a (on-premise) GitLab Nuget feed. The GitLab nuget feed is fine; I can connect VS2019 directly to it and this works fine.

I will contact support@inedo.com with the contents of the index.json and query json files.

rhessinger

Hi @RobIII,

We received the email, please give us a little bit of time to review this and we will get back to you soon!

Thanks,
Rich

atripp

Hi @RobIII ,

Thanks for sending that over; we've reviewed it, but nothing is jumping out as a problem. I'm thinking it's something else...

Can we do this?

At first, let's move this to a new topic. I'm going to lock this thread, can you reply as a new topic? The reason for this is so that we can track much easier.

Is it possible to share access to your GitLab repository? That's the easiest thing of course, but you say "on-prem" so maybe 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.

The most likely scenario is that GitLab doing something wrong/weird against the spec, but it just happens to work in Visual Studio. That was the sitaution of GitHub.

Thanks,
Alana