Topics created by andreas.unverdorben_1551 | Inedo Community Forums

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

A

Topics

A

npm package version falsely marked as vulnerable by ProGet

Watching Ignoring Scheduled Pinned Locked Moved Support
5

0 Votes

5 Posts

33 Views

A

@atripp said: ust as an FYI, I submitted two pull requests for this: Thank you very much, Alana!
A

Many timeouts in ProGet log when restoring packages

Watching Ignoring Scheduled Pinned Locked Moved Support
7

2

0 Votes

7 Posts

74 Views

A

Hi @enrico-proget_8830 , Using ngnix is probably a better solution anyway if you don't mind setting that... but the setting is now under Admin > HTTP Settings > Web Server " Edit" Thanks, Alana
A

npm install slow on proxy feed

Watching Ignoring Scheduled Pinned Locked Moved Support
3

0 Votes

3 Posts

26 Views

A

Hi Dean, we noticed that when performing an "npm install" against ProGet it will successively open ~1000 sessions. We tried a couple of values for Web.ConcurrentRequestLimit under "Administration --> Advanced Setting" (20, 50, 100, 200) and found out, that when using 100 we get the same (or even better) performance for an "npm install" compared to registry.npmjs.org. We're not exactly sure how Web.ConcurrentRequestLimit works but we assume that it has some relation to the default pool size for the SQL Server connection used by ProGet, which also seems to be 100. I just wanted to let you know, that by setting Web.ConcurrentRequestLimit to 100 the performance of "npm install" is back to normal. Best, Andreas