docker progetcore:5.3.10 - unable to push packages

jyip_5228

Hi,
Switched to progetcore due to a possible fix of DB timeouts. however found the following problem when trying to push packages via nuget.

[Exec] "C:\Txx\tools\NuGet.CommandLine.4.7.1\tools\Nuget.exe" push "C:\xxx.nupkg" -Source "https://xxxxxx/nuget/ks-nuget/" -ApiKey "xxxxxxxx"
[14:58:16][Exec] Pushing xxx.nupkg to 'https://xxxxxx/nuget/ks-nuget/'...
[14:58:16][Exec]   PUT https://xxxxxx/nuget/ks-nuget/
[14:58:16][Exec]   InternalServerError https://xxxxxx/nuget/ks-nuget/ 282ms
[14:58:16][Exec]   PUT https://xxxxxx/nuget/ks-nuget/
[14:58:17][Exec]   InternalServerError https://axxxxxx/nuget/ks-nuget/ 171ms
[14:58:17][Exec]   PUT https://xxxxxx/nuget/ks-nuget/
[14:58:17][Exec]   InternalServerError https://xxxxxx/nuget/ks-nuget/ 168ms
[14:58:17][Exec] Response status code does not indicate success: 500 (Internal Server Error).

Reverting back to the regular proget:5.3.10 works perfectly.

atripp

Hello;

Can you share the errors you're seeing in the Admin > Diagnostic Center? Those will be logged w/ the 500 errors.

Thank!

jyip_5228

Found this.

An error occurred processing a PUT request to http://xxxx/nuget/ks-nuget/: Synchronous operations are disallowed. Call ReadAsync or set AllowSynchronousIO to true instead.
 Details: System.InvalidOperationException: Synchronous operations are disallowed. Call ReadAsync or set AllowSynchronousIO to true instead.
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpRequestStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at Microsoft.AspNetCore.WebUtilities.FileBufferingReadStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Stream.ReadByte()
at Inedo.IO.StreamSearcher.FindNext(Stream stream)
at Inedo.IO.StreamSearcher.FindAll(Stream stream)+MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Inedo.Web.HttpRequestExtensions.GetPostedFilesInternal(HttpContext context)
at Inedo.Web.HttpRequestExtensions.GetPostedFiles(HttpContext context)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.PutHandler.ProcessPutRequestAsync(HttpContext context, RequestData urlData, NuGetFeed feed) in C:\InedoAgent\BuildMasterTemp\192.168.44.60\Temp\_E55466\Src\ProGet.WebApplication\FeedEndpoints\NuGet\NuGetApi.PutHandler.cs:line 42
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.ProcessRequestAsync(HttpContext context, NuGetFeed feed, String relativeUrl) in C:\InedoAgent\BuildMasterTemp\192.168.44.60\Temp\_E55466\Src\ProGet.WebApplication\FeedEndpoints\NuGet\NuGetApi.cs:line 37
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.ProcessRequestAsync(HttpContext context) in C:\InedoAgent\BuildMasterTemp\192.168.44.60\Temp\_E55466\Src\ProGet.WebApplication\FeedEndpoints\FeedEndpointHandler.cs:line 192

gdivis

Thanks for the error report. We've fixed this as PG-1816, which will be included in tomorrow's releases (ProGet 5.3.11).

mikhael_3947

Same issue on docker container (which is dotnet core too) proget.inedo.com/productimages/inedo/proget:5.3.11
I see the same issue when doing a docker push :

received unexpected HTTP status: 500 Internal Server Error

When I catch the HTTP response to PUT /v2/base/alpine/manifests/3.9 HTTP/1.1 with wireshark I can read : Could not find a part of the path '/var/proget/packages/.docker/F3'.
Also since I did a bind mount in the docker I can see that the folder F3 is not created : /var/proget/packages/.docker/F3

But docker push works with the docker image proget.inedo.com/productimages/inedo/proget:5.3.10
And F3 folder is created as expected and I can find the manifest.

gdivis

Docker uses different file operations from all of the other feeds, so it looks like we missed fixing it there. We'll look into this and get it fixed.

Thanks for trying progetcore!

gdivis

We've got this fixed. If you'd like to try it, it's available as proget.inedo.com/productimages/inedo/progetcore:5.3.12-ci.1