Proget VorSecurity VulnerabilityDetails exception with Feed Type npm

[Tom Edgar]

Hi ,

When trying to view the details of a Vulnerability when using VorSecurity, the following error occurs. There is no issue with the nuget feed, only when it is npm. It seems like it is not able to find the name of the FeedType

Can you help please?

Thanks,
Tom

Specified argument was out of the range of valid values.
Parameter name: code

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: code

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: code]
Inedo.Data.DataDomain`1.GetName(String code) +540
Inedo.ProGet.WebApplication.Pages.Vulnerabilities.VulnerabilityDetailsPage.CreateChildControls() +1272
Inedo.ProGet.WebApplication.Pages.<InitializeAsync>d__2.MoveNext() +281
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
Inedo.Web.PageFree.<ProcessRequestAsync>d__48.MoveNext() +378
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) +98
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +606
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +288

Product: ProGet
Version: 4.7.14

[Ben Lubar]

Hello Tom,

You are correct that this is caused by the npm feed type not being found. I've filed this as PG-1073 and submitted a fix for review, so it should be fixed in the next version of ProGet.