I'm directly executing the DashboardFeeds view, so I'm not using the parameter. It seems that the SUM([Package_Size] for [Feed_Size] and [Cache_Size] are the culprit. When I replace the query with [Feed_Size] = 0, [Cache_Size] = 0 then the timeouts are gone! They are just missing from the feed disk usage graph. Adding an index to NuGetPackageVersionsV2.Package_Size didn't help. The strange thing is that some pages that are not using the graph are also executing the DashboardInfo stored procedure.

I's possible the way permissions are validated in the installer is not applicable to RDS instances of SQL Server (I know a while ago there was a similar issue with Azure databases since the particular query we used to check was disallowed). Can you try pointing at a local SQL Server Express instance, then changing the connection string in the %PROGRAMDATA%\Inedo\SharedConfig\ProGet.config post-install (and then restart web service and ProGet service)?

Hi Tod, Thanks for looking into this. I just checked and can confirm that the last time we received this error it matched up with an app pool recycle. I'm not sure yet whether this is the source of all our timeouts, but that's certainly given us something to work with. I'll post again if we suspect any other Proget related issues. Thanks again.

Hello, Just following up: The root cause of Windows images from connectors not working is that ProGet was not telling the connector that it supported v2 manifests, and the v1 manifests generated for Windows images by Docker Hub are broken. This is PG-1351.

We can't reproduce this - in all cases we've tried the casing of supplied package ID's does not matter in requests to ProGet. If you capture the failing requests using Fiddler and attach them to a ticket, we can hopefully find out why it is not working for you.

Thanks for the usecase - that's interesting and a good point in favor of doing this. Unfortunately after a brief review I've found that it's a little more technically complex than we first anticipated. I still think that we will do it, but it isn't something we can just drop in the next release.

Alana, thanks. I didn't realize those variables did not appear in that list, thought that was all variables. In any event, knowing they are app settings variables helps. Thanks!

I think that guide is more for when you host a domain controller in azure as IaaS. Im after connecting to Azure AD in the form of SAML, or OpenIDConnect (Federation) I'll keep an eye on release notes to see when SSO gets released. Thanks

I'm afraid I don't really understand the requirements for what you're trying to accomplish... Here are the differences between the two extensibility points: A Package Filter allows all locally-stored ProGet packages to be filtered from being shown in feeds by additional logic. A Package Access Rule Allows for rules to block downloads of packages based on additional logic. The Package Access Rule is used by the Whitesource extension, so you can reference how that works. We don't have any publicly available uses of Package Filters; it was incorporated for a very specific usecase with publicly-available feeds.

Yes, it just involves changing the license key. Please refer to License Key Management

It is a working feature, but there are some known issues (PG-1343 and PG-1344) that we will have fixed soon. You can find the documentation here.

Hi Clint, Sorry for the slow response. There is no current way to do this at the role level, but we could possibly add this as a feature. If you'd like it, check out our new feature request process, and we can see about assessing it. Thanks!

Good questions; You can configure ProGet to block packages with "unassessed" vulnerabilities; this is not the default configuration because a lot of times vulnerabilities are discovered after you've already been using a package anyways That's true, but maybe we could expand webhooks? I'm not sure, but it seems like it could be a feature request if it's something you'd actually want to use, etc.

Hello; just to let you know, the Inedo ProGet Plugin for Jenkins has been updated, and may work better. Have you had an progress onthis otherwise?

Hi Benedikt, We haven't been able to reproduce this, and I don't see any instances in the installer code where SQL connections are not released immediately after being used. What do you mean that it was not possible to install SQL Express with our installer? Did it fail with an error, or was the option disabled?

Just to be clear... you can't go from Windows >> Linux, because it's PostgreSQL vs SQL SErver. But if you're already on Linux edition, you can just upgrade the container; the database files and package stores are already configured to point outside the container.

You can request a free key at https://my.inedo.com/

BuildMaster does all of these things, it's almost as if you've rewritten the feature page for it in bullet form :) Most downloaders start by getting a super simple app deployed and then expand on it. Here is the "starter" tutorial we recommend (it should hopefully make sense even if you don't use .NET or IIS): https://inedo.com/support/tutorials/buildmaster/deployments/deploying-a-simple-web-app-to-iis

Hello all, ProGet 5.1.7 fixes an additional issue that was causing SemVer2 NuGet packages to fail to download: PG-1329

The tracking issue for this is here: PG-1337