Hello @atripp

I'm confused.
I had several nuggets that could not be pushed via the command and I did not verify the renaming to .zip on all of them.
When I tried the "Drop Path" method I tried on one that I hadn't checked.

With your message that it's been 10 years since you've had a problem like this. I started again from scratch and I noticed that this Nuget indeed does not open with windows but it opens with 7zip. What's more, I asked our teams and this nuget is not necessarily good.

What put me in error was that it was in our old binary manager and that our new binary manager accepts it.

I'll be able to do some more tests on replication.

Thank you for your help

Hello @atripp

Sorry for taking so long to reply, I hadn't seen the message. Here are my answers:

We have a "Nuget-Writer" tool based on Microsoft libraries and the Coap tool.
Yes, if we rename the file to .zip we can open it with Windows and 7zip.

I tried the "Drop Path" method and here are the logs:

DEBUG: 2023-10-10 15:14:54Z - Scanning for packages in D:\Bulk-import...
DEBUG: 2023-10-10 15:14:54Z - Importing 1 files from the drop path...
DEBUG: 2023-10-10 15:14:54Z - Found D:\Bulk-import\My_Nuget_1.2.2.6.nupkg
WARN : 2023-10-10 15:14:54Z - Error installing package: End of Central Directory record could not be found.
DEBUG: 2023-10-10 15:14:54Z - Deleting files...
DEBUG: 2023-10-10 15:14:54Z - Indexed 0 packages in Demo_NuGet feed.

Thank you @stevedennis.

I’ll check my .nupkg.
Because I can’t upload it with a script or interface.

Hello @stevedennis,

Thank you for your answer.
I maybe in this rare cases where the stream can be corrupted.
Because the file is a .nupkg and it has already been uploaded to Klondike.
Would ProGet have additional checks that don’t exist at Klondike?
I was wondering too, does ProGet have a limit on file size?

Hello,

I try to push a Nuget via the command given in ProGet.
But after 3 tentive the powershell command ends with an Internal Server Error 500.
In the ProGet error message I have the following message:

An error occurred processing a PUT request to http://URL_My_Feed: End of Central Directory record could not be found.

And the Details:

System.IO.InvalidDataException: End of Central Directory record could not be found.
at System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()
at System.IO.Compression.ZipArchive..ctor(Stream stream, ZipArchiveMode mode, Boolean leaveOpen, Encoding entryNameEncoding)
at System.IO.Compression.ZipArchive..ctor(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)
at Inedo.ProGet.Feeds.NuGet.ParsedNuGetPackage.Read(Stream stream)
at Inedo.ProGet.Feeds.NuGet.NuGetFeed.InstallOrUpdatePackageAsync(Stream stream, Boolean calculateHash, Boolean cached, Boolean install, Boolean overwrite, Nullable1 publishDate, Nullable1 listed, Nullable`1 downloadCount, Boolean promoted)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.PutHandler.ProcessPutRequestAsync(HttpContext context, WebApiContext apiContext, RequestData urlData, NuGetFeed feed)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.ProcessRequestAsync(HttpContext context, WebApiContext apiContext, NuGetFeed feed, String relativeUrl)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetFeedHandler.ProcessRequestAsync(HttpContext context, WebApiContext apiContext, NuGetFeed feed, String relativeUrl)
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.ProcessRequestAsync(HttpContext context)

I specify that just before I managed to push other nuget with the same command.

Thank you in advance for your help