Posts made by jaroslav.malec_8365

We regularly push to our Proget from CI jobs. As a transient failure flags the job as failed, it is less trivial to overcome than if run from a keyboard.

Happens in about 3-10% of cases.

• On Debian
• In Docker
• With Postgres in a separate container

Logs are empty AFAIK. (In case some should be present, I'd like to know where)

Redacted CI output:

Running with gitlab-runner 11.7.0 (8bb608ff)
  on BlackieTestServer 4eafc0bc
Using Shell executor...
Running on BLACKIEMACHINE...
Cloning repository...
Cloning into 'C:/Users/Blackie/builds/4eafc0bc/0/#####/#####/#####-hardware'...
Checking out 69d3afdf as master...
Skipping Git submodules setup
$ Set-ExecutionPolicy Unrestricted -Scope Process
$ ci/Add-NugetConfig.ps1
$ dotnet pack #####.#####.Hardware\#####.#####.Hardware.csproj
Microsoft (R) Build Engine version 15.9.20+g88f5fadfbe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restoring packages for C:\Users\Blackie\builds\4eafc0bc\0\#####\#####\#####-hardware\#####.#####.Hardware\#####.#####.Hardware.csproj...
  Generating MSBuild file C:\Users\Blackie\builds\4eafc0bc\0\#####\#####\#####-hardware\#####.#####.Hardware\obj\#####.#####.Hardware.csproj.nuget.g.props.
  Generating MSBuild file C:\Users\Blackie\builds\4eafc0bc\0\#####\#####\#####-hardware\#####.#####.Hardware\obj\#####.#####.Hardware.csproj.nuget.g.targets.
  Restore completed in 516.99 ms for C:\Users\Blackie\builds\4eafc0bc\0\#####\#####\#####-Hardware\#####.#####.Hardware\#####.#####.Hardware.csproj.
  #####.#####.Hardware -> C:\Users\Blackie\builds\4eafc0bc\0\#####\#####\#####-hardware\#####.#####.Hardware\bin\Debug\netstandard2.0\#####.#####.Hardware.dll
  #####.#####.Hardware -> C:\Users\Blackie\builds\4eafc0bc\0\#####\#####\#####-hardware\#####.#####.Hardware\bin\Debug\net471\#####.#####.Hardware.dll
  Successfully created package 'C:\Users\Blackie\builds\4eafc0bc\0\#####\#####\#####-hardware\#####.#####.Hardware\bin\Debug\#####.#####.Hardware.0.3.0.nupkg'.
$ dotnet nuget push -k $Env:NUGET_SOURCE_APIKEY -s $Env:NUGET_SOURCE_URL #####.#####.Hardware\bin\Debug\#####.#####.Hardware*.nupkg
info : Pushing #####.#####.Hardware.0.3.0.nupkg to 'https://proget.#####.cz/nuget/Nuget/'...
info :   PUT https://proget.#####.cz/nuget/Nuget/
info :   BadRequest https://proget.#####.cz/nuget/Nuget/ 205ms
error: Response status code does not indicate success: 400 (There must be exactly one package.).
ERROR: Job failed: exit status 1

A subsequent run succeeds with:

$ dotnet nuget push -k $Env:NUGET_SOURCE_APIKEY -s $Env:NUGET_SOURCE_URL #####.#####.Hardware\bin\Debug\#####.#####.Hardware*.nupkg
info : Pushing #####.#####.Hardware.0.3.0.nupkg to 'https://proget.#####.cz/nuget/Nuget/'...
info :   PUT https://proget.#####.cz/nuget/Nuget/
info :   Created https://proget.#####.cz/nuget/Nuget/ 360ms
info : Your package was pushed.
Job succeeded

Product: ProGet
Version: 5.1.23

We upgraded our Docker Proget image from 5.1.11 to 5.1.20 and pushing no longer works. Same behaviour was seen in 5.1.19.

Note that the Postgres image (and volume) were untouched. The DB volume was setup along with some older Proget 5.1.* when we first got it working a few months ago.

From my limited knowledge and from the error description I assume there must have been a DB interface addition between 5.1.11 and 5.1.19. This is unexpected for a patch release.

Diagnostic center entry:

Logged:

01/17/2019 10:22:58

Level:

Error

Category:

Web

Message:

An error occurred processing a PUT request to http://......../nuget/Nuget/: 42883: function NuGetPackagesV2_CreateOrUpdatePackage(@Feed_Id => integer, @Package_Id => text, @Version_Text => text, @FullVersion_Text => text, @Published_Date => timestamp without time zone, @Package_Size => bigint, @PackageHash_SHA1_Bytes => bytea, @PackageHash_SHA512_Bytes => bytea, @TargetFrameworks_Text => text, @Nuspec_Bytes => bytea, @Symbols_Indicator => text, @Source_Indicator => text, @Cached_Indicator => text, @Listed_Indicator => text, @Download_Count => integer, @LatestVersion_Text => text, @LatestStableVersion_Text => text, @SymbolFiles_Xml => xml, @ForceSetLatestVersions_Indicator => text, @NuGetPackageV2_Id => integer, session_user_name => text) does not exist

Details:

Npgsql.PostgresException (0x80004005): 42883: function NuGetPackagesV2_CreateOrUpdatePackage(@Feed_Id => integer, @Package_Id => text, @Version_Text => text, @FullVersion_Text => text, @Published_Date => timestamp without time zone, @Package_Size => bigint, @PackageHash_SHA1_Bytes => bytea, @PackageHash_SHA512_Bytes => bytea, @TargetFrameworks_Text => text, @Nuspec_Bytes => bytea, @Symbols_Indicator => text, @Source_Indicator => text, @Cached_Indicator => text, @Listed_Indicator => text, @Download_Count => integer, @LatestVersion_Text => text, @LatestStableVersion_Text => text, @SymbolFiles_Xml => xml, @ForceSetLatestVersions_Indicator => text, @NuGetPackageV2_Id => integer, session_user_name => text) does not exist
at Npgsql.NpgsqlConnector.DoReadMessageAsync (System.Threading.CancellationToken cancellationToken, Npgsql.DataRowLoadingMode dataRowLoadingMode, System.Boolean isPrependedMessage) [0x002d7] in <4985dea8374f4819bebb7847d95ad483>:0
at Npgsql.NpgsqlConnector.ReadMessageWithPrependedAsync (System.Threading.CancellationToken cancellationToken, Npgsql.DataRowLoadingMode dataRowLoadingMode) [0x001c3] in <4985dea8374f4819bebb7847d95ad483>:0
at Npgsql.NpgsqlConnector.ReadExpectingAsync[T] (System.Threading.CancellationToken cancellationToken) [0x00074] in <4985dea8374f4819bebb7847d95ad483>:0
at Npgsql.NpgsqlDataReader.NextResultInternalAsync (System.Threading.CancellationToken cancellationToken) [0x003b6] in <4985dea8374f4819bebb7847d95ad483>:0
at Npgsql.NpgsqlDataReader.NextResultAsync (System.Threading.CancellationToken cancellationToken) [0x0014a] in <4985dea8374f4819bebb7847d95ad483>:0
at Npgsql.NpgsqlCommand.ExecuteAsync (System.Threading.CancellationToken cancellationToken, System.Data.CommandBehavior behavior) [0x003d8] in <4985dea8374f4819bebb7847d95ad483>:0
at Npgsql.NpgsqlCommand.ExecuteDbDataReaderInternalAsync (System.Data.CommandBehavior behavior, System.Threading.CancellationToken cancellationToken) [0x000f1] in <4985dea8374f4819bebb7847d95ad483>:0
at Npgsql.NpgsqlCommand.ExecuteDbDataReaderAsync (System.Data.CommandBehavior behavior, System.Threading.CancellationToken cancellationToken) [0x000a7] in <4985dea8374f4819bebb7847d95ad483>:0
at Inedo.Postgres.WrappedPgCommand.ExecuteDbDataReaderAsync (System.Data.CommandBehavior behavior, System.Threading.CancellationToken cancellationToken) [0x001db] in <94aa300a575f4466b4255c21e38a03f6>:0
at Inedo.Data.DatabaseContext+DbResult.CreateAsync (System.Data.Common.DbCommand command, Inedo.Data.DatabaseContext context, System.DateTimeOffset startTime, System.Diagnostics.Stopwatch stopwatch) [0x00082] in <3fa12eb0dd0e47108f8eb32ec5ace40f>:0
at Inedo.Data.DatabaseContext.ExecuteInternalAsync (System.String storedProcName, Inedo.Data.GenericDbParameter[] parameters) [0x0021e] in <3fa12eb0dd0e47108f8eb32ec5ace40f>:0
at Inedo.Data.DatabaseContext.ExecuteNonQueryAsync (System.String storedProcName, Inedo.Data.GenericDbParameter[] parameters) [0x0007b] in <3fa12eb0dd0e47108f8eb32ec5ace40f>:0
at Inedo.ProGet.Feeds.NuGet.NuGetFeed.InstallOrUpdatePackageAsync (System.IO.Stream stream, System.Boolean calculateHash, System.Boolean cached, System.Boolean install, System.Boolean overwrite, System.Nullable1[T] publishDate, System.Nullable1[T] listed, System.Nullable`1[T] downloadCount, System.Boolean promoted) [0x00b20] in <6fbd9e1a5a444466a7d28481b2a9b416>:0
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi+PutHandler.ProcessPutRequestAsync (System.Web.HttpContext context, Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi+RequestData urlData, Inedo.ProGet.Feeds.NuGet.NuGetFeed feed) [0x00170] in <b7cd06db3e5a4b62829242d1b5a27e91>:0
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.ProcessRequestAsync (System.Web.HttpContext context, Inedo.ProGet.Feeds.NuGet.NuGetFeed feed, System.String relativeUrl) [0x0019b] in <b7cd06db3e5a4b62829242d1b5a27e91>:0
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler+FeedRequestHandler.ProcessRequestAsync (System.Web.HttpContext context) [0x000a4] in <b7cd06db3e5a4b62829242d1b5a27e91>:0

Product: ProGet
Version: 5.1.20

Pushing package versions differing in the prerelease version number appears defunct.

The issue may be reproduced as follows:

1. Push a Nuget package 1.0.0-beta.1
2. Push a Nuget package 1.0.0-beta.2

What is expected:

• To have two versions of the package present in the feed.

What actually happens:

• When the newer package is pushed, the old file is overwritten, but the old name/version remains.

This problem also happens when pushing via Drop path.

Product: ProGet
Version: 5.1.11

Hi,

just writing to let you know that this is a very serious issue for us. Up to the point of not using ProGet and switching to a different solution.

In case this is resolved we shall even consider buying a subscription.

Cheers