Problems with NPM connector

[Diego]

I'm facing several problems with the NPM connector. First of all and, as mentioned in question 4302 by chris the packages are simply not listed. I've run the FullNpmConnectorIndex scheduled task several times but still the same. The task runs fine, just outputing the warnings about versions property. However in the event log nothing get's registered (in v3.8.6 each package generated a message regarding whether it was created or updated).

Additionally, the IncrementalNpmConnectorIndex is failing with the following details:

DEBUG: Getting metadata from https://registry.npmjs.org/-/all/since?stale=update_after&startkey=1455702501720 ERROR: Error processing JSON: System.Exception: uninclused at Inedo.ProGet.ScheduledTasks.Npm.NpmConnectorIndexScheduledTaskBase.<IndexConnectorAsync>d__1.MoveNext()

If you try to access a specific package page (using the /<feed>/<package>/<version> convention) you get part of the page but not the versions. And in the errors console you can see a classical An error occurred in the web application: Object reference not set to an instance of an object. with the following stack trace:

URL: http://myserver:81/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Pages.Npm.Feeds.NpmPackageVersionPage/GetFullPackageInfo Referrer: http://myserver:81/npm-feeds/mynpm/npm/3.7.2 User: MorpheAdmin User Agent: Mozilla/5.0 (Windows NT 6.3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36 Stack trace: at Inedo.ProGet.WebApplication.Pages.Npm.Feeds.NpmPackageVersionPage.<GetFullPackageInfo>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter´1.GetResult() at Inedo.Web.Handlers.JsonDataHttpHandler.AsyncHandler.<ProcessRequestAsync>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

Finally, when you try to install anything from the npm feed in proget you end up with errors regarding no compatible version found (when you don't specify a version correctly) or version not found (when you target a specific version).

At this point the NPM feed is totally useless, so I'd really apreciate some insight on what's going on and what can be done to solve it.

Product: ProGet
Version: 4.0.5

[Tod]

The "Object reference not set to an instance of an object" errors are caused by underlying database timings due to async connections not being closed properly which is fixed in the current v4.0.7 version.

The incremental connector indexer will require an update to 4.0.8 once its released. The npm registry modified the response of the /all/since endpoint which is used to do the incremental update. We have a fix for that working internally. Simply use the full indexer as a workaround (it just takes a bit longer ;)).

On top of all this, as of yesterday's definitions, Windows Defender now incorrectly flags our installers (and even manual install .zip files from years ago... somehow...) as a trojan which we are trying to resolve ASAP. So if you download 4.0.7 from our site (and it's signed by Inedo) be assured that it is not actually a trojan.

[Diego]

Today we updated to v4.0.8 but unfortunately issues are still preventing us from using the NPM feed. Nothing get's listed even though the full or incremental updates were run several times; even more, the connector shows the right count of packages but those are not present for listing or download. At this point we have no other option but downgrading to 3.8.6 which has proved to work fine, which is very frustrating. Has anyone else had troubles with NPM connectors in v4 releases? I'm quite concerned this is not working.

The problem when accessing a specific version still occurs

URL: http://myserver:81/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Pages.Npm.Feeds.NpmPackageVersionPage/GetFullPackageInfo Referrer: http://myserver:81/npm-feeds/mynpm/npm/3.7.1 User: MorpheAdmin User Agent: Mozilla/5.0 (Windows NT 6.3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36 Stack trace: at Inedo.ProGet.WebApplication.Pages.Npm.Feeds.NpmPackageVersionPage.<GetFullPackageInfo>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter´1.GetResult() at Inedo.Web.Handlers.JsonDataHttpHandler.AsyncHandler.<ProcessRequestAsync>d__6.MoveNext()

[Diego]

Dismiss my recent answer

It works fine

At some point the connector was removed from the feed which explains why nothing got listed even though the connector was fine. I'm really sorry for this!

Thanks for the support!