These will be included in the next maintenance release as per this issue: PG-1406

You can download the latest (v41 at the time of this post) from here: https://inedo.com/support/documentation/inedoagent/versions

PowerShell converts 10GB into 10737418240 - OtterScript doesn't do this automatically, you'd have to do $PsEval(10GB) if you wanted the equivalent, but it's best to just put the number in directly I would think.

You could use the Variables Management API for this:

https://inedo.com/support/documentation/otter/reference/api/variables

We cannot reproduce this behavior.

How are you verifying that the older package isn't in the feed? Note that the Feed Overview page only lists the latest version, you have to browse to the versions tab once you select that package to actually see all the versions.

Thank you for the report; it looks like the extension was migrated correctly but never officially released to our extension feed...

I'll have someone release it ASAP

A 401 means that npm requires authentication which was not supplied, visit Feeds > Connectors > [edit/create npm connector] and enter a username/password to connect to the external registry.

This was resolved in the latest release of Otter (v2.0.12 at the time of posting).

This is configured in: Admin > Change User Directory (LDAP) > Advanced > Active Directory (New)

There are ways to test/debug on that page as well.

These are available on the All Versions page: https://inedo.com/proget/versions

Is this user a direct member? If not, you need the latest InedoCore extension (v1.0.8 as of a few minutes ago) and make sure to enable recursive search in its advanced configuration.

Make sure to delete the C:\ProgramData\upack directory as well

This is a small bug in the extension (it identifies as a different version than it was released as) that occurred during an internal transition... each of those 2 extensions will no longer show as "update available" once their next versions are released.

As far as I'm aware, the original issue in this thread has been resolved long ago.

If there is a new issue with pulling connector packages, please post a new question.

This took a while to track down, but that error message is ultimate caused by having an extension that fails to load along with a value set for Extensions.BuiltInExtensionsPath, and the error message will be fixed as part of issue: ILIB-52

However, this error is only generated when the extensions manager is initialized, which occurs when the integrated web server (or IIS application pool) is restarted. This means that either the timeout you're experiencing causes the website to restart, or the timeout is caused by the web server restarting.

You could try setting Diagnostics.MinimumLogLevel to 0 temporarily to get debug logging, or examine the Windows Event Log to see if there are any .NET errors that cause the web application to restart.

Make sure the following configuration values in Admin > Advanced Settings are set to an accessible directory (note that the defaults from the installer are shown here, double-check that they are valid in your installation):

• Extensions.ExtensionsPath - C:\Program Files\ProGet\Extensions
• Extensions.ServiceTempPath - C:\ProgramData\ProGet\ExtensionsTemp\Service
• Extensions.WebTempPath - C:\ProgramData\ProGet\ExtensionsTemp\Web

The connection string is in a different place yes, but unless you changed it from the value it was, that shouldn't affect timeouts.

My guess is that the SQL Server service just needs to be restarted.

Is your feed configured to strip symbols and/or source code from the package?

The tracking issue for this is here: PG-1337

Please refer to the Upgrading Extensions section of the v6.0 upgrade notes.