Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. andreas.unverdorben_1551
    3. Topics

    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 Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 7
    • Groups 0

    Topics

    • A

      npm package version falsely marked as vulnerable by ProGet

      Watching Ignoring Scheduled Pinned Locked Moved Support
      3
      0 Votes
      3 Posts
      16 Views
      A
      Hi Steve, thanks for the explanation. I also think creating a PR for GHSA would be the best way to go. Since your company is incorporating GHSA into your product I think it's up to Inedo to improve GHSA by creating this PR, thus improving your product for you customers. Thanks, Andreas
    • A

      Many timeouts in ProGet log when restoring packages

      Watching Ignoring Scheduled Pinned Locked Moved Support
      7
      2
      0 Votes
      7 Posts
      74 Views
      atrippA
      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
    • 1 / 1