500 - Internal server error. on downloading a package from default feed

[Sam Chen]

Hi,

we're getting 500 - Internal server error. on downloading a package from default feed.
below is the error from the admin console

System.NotSupportedException: This stream does not support seek operations.
at System.Net.ConnectStream.get_Length()
at System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()
at System.IO.Compression.ZipArchive.Init(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.GetHandler.StripSymbols(Stream packageStream)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.GetHandler.<TransmitPackageAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.GetHandler.<ProcessGetRequestAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.<ProcessRequestAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.<ProcessRequestAsync>d__8.MoveNext()

Product: ProGet
Version: 4.7.11

[Tony]

I ran into a similar problem. This started happening right after i updated the Amazon Extension from version 4.6.1 to version 4.6.3. After i reverted to the old version, it stopped having problems.

This only happened with specific packages (due to the package naming i believe) that are using S3 as storage.

[Ben Lubar]

Hello Sam,

This should be fixed in version 4.6.4 of progetx-amazon, which is currently being tested.