Internet Explorer is no longer supported. Many things will still work, but your experience will be degraded and some things won't function. Please use a modern browser such as Edge, Chrome, or Firefox.

Issues Overview

This application is not configured to allow new issues to be created.

PG-1825 6.0.0 Bug Open Add user-friendly container image urls
Should have same format as packages
PG-2005 5.3.37 Bug Completed FIX: POM files downloaded from Maven feeds may be saved with empty contents
PG-2004 5.3.36 Bug Awaiting Release FIX: POM files from maven connectors may 404 on request (regression from PG-1995)
PG-2002 5.3.36 Bug Awaiting Release FIX: Optimized move is sometimes not performed on local filesystems when it can be
PG-1999 5.3.36 Bug Awaiting Release FIX: Dependencies for remote packages on PyPi feeds may not be displayed in UI
PG-2000 5.3.36 Bug Awaiting Release FIX: "Enterprise Only" Message appears on Server Cluster Page even if you have Enterprise Edition
PG-2001 5.3.36 Bug Awaiting Release FIX: Unnecessary additional level of buffering on Docker image layer uploads can cause large uploads to take a long time to complete
PG-1998 5.3.35 Bug Awaiting Release FIX: Asset API uses incorrect secured tasks for some actions
PG-1995 5.3.35 Bug Awaiting Release FIX: Potential 500 error when using PUT to maven feeds w/ Amazon S3
``` An error occurred processing a PUT request to https://SERVER/maven2/artifact-path: Specified method is not supported. System.NotSupportedException: Specified method is not supported. at Inedo.ProGet.Extensions.AWS.PackageStores.S3WriteStream.set_Position(Int64 value) at Inedo.ProGet.Extensions.AWS.PackageStores.WritablePositionStream.set_Position(Int64 value) at Inedo.ProGet.Feeds.Maven.MavenFeed.d__26.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.ProGet.Feeds.Maven.MavenFeed.d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.ProGet.WebApplication.FeedEndpoints.Maven.MavenFeedHandler.d__1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.d__8.MoveNext() ```
PG-1990 5.3.34 Bug Completed FIX: NuGet v2 connector queries are not getting the $skip and $top values forwarded to them
PG-1991 5.3.34 Bug Completed FIX: Filter feeds in Feed Disk Usage on homepage if user doesn't have access to feeds
PG-1993 5.3.34 Bug Completed FIX: Package History Page - Deployment URL not clickable
PG-1992 5.3.34 Bug Completed FIX: Put Metadata Request for Maven may fail on Linux
In `MavenFeedHandler.cs#173`, the following line is yielding a "root element not found" error on .NET5/Docker: `var xdoc = XDocument.Load(context.Request.InputStream);` Should it should be changed to something like? `var xdoc = XDocument.Load(context.Request.GetUnlimitedInputStreamAsync());`
PG-1989 5.3.34 Feature Completed Ensure current user uses dbo schema when performing database upgrades
This can just be added to the untracked DDL-DML scripts. ``` IF (SCHEMA_NAME() <> 'dbo') BEGIN DECLARE @SQL NVARCHAR(MAX) = 'ALTER USER [' + CURRENT_USER + '] WITH DEFAULT_SCHEMA = [dbo]' PRINT 'Changing default schema ("' + SCHEMA_NAME() + '") to dbo via: ' + @SQL EXEC sp_executesql @SQL PRINT 'Schema changed.' END ```
PG-1987 5.3.34 Bug Completed FIX: $PackageProperty() does not properly return releaseNotes on NuGet packages
PG-1988 5.3.34 Bug Completed FIX: Package Promotion across s3 feeds may yield "HashStream does not support seeking" error
Both my source feed and target feed are on aws s3 and I am getting an error that is apparently from the s3 buckets. I created 2 feeds, a prerelease feed and full release feed. Both Nuget. The prerelease feed is an internal feed, and the release feed is a promotion feed. I updated the aws settings on the server (the proget installation is on EC2) so i tested the upload/download feature of both feeds and verified the files were in s3 properly. (side note: I have been using s3 buckets for storage for a while with other feeds, so this isn't a new thing, however I wanted to make sure I did my due diligence before submitting a ticket). I uploaded a test package to the prerelease feed and attempted to promote it to the release feed. I get this error. "An error occurred promoting the package: HashStream does not support seeking" (see attached image). Troubleshooting steps Updated the Prerelease and release feeds storage packages from local storage to s3 and back in a combination to see what specifically was not working - s3 -> s3 : failed - local -> local: passed - local -> s3: passed - s3 -> local: failed
PG-1984 5.3.33 Feature Awaiting Release Expose Users_SetPassword in Native API
PG-1983 5.3.33 Feature Awaiting Release Add option to crash service if a replication job gets stuck
PG-1985 5.3.33 Bug Awaiting Release FIX: Target virtualFile resource name is truncated on Upack Feeds
"We found a little bug on Upack virtual package feeds. We try to use "virtualFile" content items. When the virtualpackage is fetched or construct the name of file (last part of URL) is truncated of one character at the end. We attached to reproduce this litlle bug, the original vpack file, the screenshot of package files details and the resulting upack package."
PG-1986 5.3.33 Feature Awaiting Release Improve License Key Expiration Notifications
PG-1977 5.3.33 Feature Not Implemented Improve UI for advanced options in connectors
Currently, the advanced options are implemented by feed type. A lot of these options are shared amongst different feed types and should be combined in the UI.
PG-1945 5.3.32 Feature Awaiting Release Personal API Keys [v6 Preview Feature]
From the discussion: https://forums.inedo.com/topic/3204/proget-feature-request-api-key-admin-per-user **User Drop Down (from your screenshot)** * Add "Personal API Keys" link above "Change Password" * Show link only to Authenticated users (i.e. Anonymous can't see it) * Link navigates to `/my/api-keys` **View Package Page** * *should we also link to Personal API Keys? Where to mention this?* **Personal API Keys (new page)** * Show InfoBox based on user type (see below) * Show table with three columns: Api Key, Description, and delete button (❌) * Clicking on API Key opens a modal that allows editing the description * "Create API Key" Button works as above (only description allowed) **Messages For Admins** This page shows only API keys with "Feed API" permissions that impersonate your username ({username}), and is intended for non-administrators to manage their own API keys. Because you have `Admin_ConfigureProGet` permission, you can [manage all API Keys in ProGet]. **Messages For Non-Admins** *Something about `:`? This page allows you to manage API Keys that ...?*
PG-1980 5.3.32 Bug Awaiting Release FIX: Intermittent errors when using connectors to PyPi.org
This happens because the RSS based API endpoint gets out of date with the simple API endpoint causing data to be missing.
PG-1981 5.3.32 Bug Awaiting Release FIX: VSIX replication fails when a package does not have four version number components
See EDO-7770 for log file. ``` ERROR: 2021-06-16 12:52:04Z - Error pushing remote package <>:1.7.11.-1: System.ArgumentOutOfRangeException: Version's parameters must be greater than or equal to zero. Parameter name: revision at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument) at System.Version.TryParseComponent(String component, String componentName, VersionResult& result, Int32& parsedComponent) at System.Version.TryParseVersion(String version, VersionResult& result) at System.Version.Parse(String input) at Inedo.ProGet.Feeds.Vsix.VsixFeed.d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.ProGet.Service.FeedReplicator.d__36.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Inedo.ProGet.Service.FeedReplicator.d__27.MoveNext() ```
PG-1979 5.3.32 Bug Awaiting Release Improve restart required UI
* Display Restart Needed Banner (using Config) for Web and Service; clear upon application start-up * Link to page that provides instructions on how to restart (Docker manual, Windows go to Service page) * Remove restart when not needed