SqlException

[Guest]

Are you not receiving our responses via email? We've sent 2 responses to both of your support tickets that indicate this is likely the result of a bug resolved in the latest version of ProGet.

[Guest]

Yes. I have seen the email. Thanks.

[Guest]

Hi,

As suggested we have upgraded to version 4.0.10, but still the error persists.

I analyzed the database script and found what is the issue.

Current scenario is we have two feeds created npm and npm-delegate (both of npm type)
So If we register a npm package name say bower first time in npm feed it works. Now if again try to register npm package bower in npm-delegate feed, it throws error. The reason I think is below.

In the database script npmFeeds_setTagVersion, it executes below query like

Select package_id from npmpackages where feed_id = <feed id> and package_name = <package name>

• So in the above query if it doesn't find the package_id it gives error. This happens if the npm package is already registered in any of npm feed and we try to register the same package again in another npm feed, it gives error.

Hope this helps to understand the issue. so please suggest what is the solution for the above.

Regards
Junaid

[Guest]

This should be resolved in ProGet v4.0.13, releasing today!

[Guest]

Hi,

We downloaded the latest version, but the issue still persists.

It seems a new column scope_name has been added to the npmpackages table.

But whenever we add any npm package it does not populate scope_name column.

Regards
Junaid

[Guest]

We researched this a bit more, and cannot reproduce; can you show the exact npm client commands you used against the two feeds?

[Guest]

We are using the command

npm publish <local package path>

For example

npm publish c:\npm\angular

Regards
Junaid

[Guest]

Can you give the entire sequence of commands that cause this error (along w/ a package that you used, including the feednames/arguments)? When we published the same package to two different feeds, we did not find a problem.

[Guest]

Hi ,

Below are the steps to add to npm and npm-delegate feed

1. Adding angular package to npm feed

npm config set registry https://proget.xyz.com/npm/npm
npm config set always-auth true
npm adduser
npm publish c:\npm\angular


2. Adding angular package to npm-delegate feed

npm config set registry https://proget.xyz.com/npm/npm-delegate
npm config set always-auth true
npm adduser
npm publish c:\npm\angular

[Guest]

Thanks!

We will have this fixed in ProGet 4.0.14, which will be released within the hour.