ProGet 6.0.10. Probable bug in npm?

[ab.korneev_0401]

Hello!

I'm trying to evaluate ProGet as caching package repository for my company.
Currently I'm running Free Edition Version 6.0.10 (Build 1) in docker container.
Public Nuget feed I've created works perfectly without any issues.

But when I'm trying to deal with npm feed I've encountered a problem (probably bug in this ProGet version?).
Feed was created as public caching feed and connector is pointing to some "upstream" npm repository (not registry.npmjs.org)

Some packages (for example npm itself and it looks like all unscoped packages) are being installed correctly by npm client using that upstream directly, but fails to install through ProGet using the same upstream.
When inspecting traffic from Proget to upstream repository I've found that instead of http://upstream.address/npm/-/npm-8.5.4.tgz ProGet sends request http://upstream.address/npm/, and thus doesn't get expected package.
But some other packages - for example @types/jasmine (and it seems like all scoped packages) are installed correclty through ProGet and traffic inspection shows correct requests issued by ProGet like http://upstream.address/@types/jasmine/-/jasmine-3.10.3.tgz

Could you please help?

[atripp]

Hi @ab-korneev_0401 ,

The npm API is very complicated behind the scenes, and third-party repositories often have bugs that cause odd behaviors when used via connector. Unfortunately it's really hard to say or figure out what's happening with out debugging.

If you can provide us with reproduction instructions like,

1. create npm feed in ProGet
2. Connect to http://upstream.address
3. Try to download the xyz package

Then we can attach a debugger to ProGet and see where it's failing.

If http://upstream.address is sensitive or requires authentication, you can email details to support at inedo dot com. Make sure to put [QA-797] in the title, and tell us when you respond so we can fish out the address.

Cheers,
Alana

[ab.korneev_0401]

Hi, @atripp

Unfortunately, that upstream in private network and it is not accessible from internet. So it is impossible for you do debug using it directly. If you can provide me with some "debug" docker image of ProGet - I can try to reproduce problem and give you back some debug log it will create.

[NanciCalo]

hi @ab-korneev_0401 ,

By "debugging", we mean running the ProGet code inside of Visual Studio's "debug mode". That will show the errors let us see quickly how to fix them. I'm afraid it's not easy to identify the problem without it, since it's very likely a bug in the third-party repository you're using.

Since it's not possible to provide that information, can you...

1. create a server on AWS LightSail (or similar cloud service)
2. Install the same type of third-party repository software and configure it in same manner
3. upload one or two packages that reproduce the problem
4. verify the problem in ProGet

Then, send us the information of the server, and we can look at it through the debug mode