Latest version of package not showing in proget

[Brian]

Hello,

The latest version of a package not showing in proget.

I restarted the service it just in case it is an indexing error, and I also reset IIS. I also set the Rebuild to true. It's having problems opening the zip. These are nuget packages I'm creating from buildmaster. The settings hasn’t changed. Also I can’t seem to make it re-read these files. This is the error:

Can not access a closed Stream:
System.IO.Compression.DeflateStream.Flush()
at MS.Internal.IO.Packaging.CompressStream.Flush()
at MS.Internal.IO.Packaging.CompressStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at MS.Internal.IO.Zip.ZipIOLocalFileBlock.Dispose(Boolean disposing)
at MS.Internal.IO.Zip.ZipIOLocalFileBlock.Dispose()
at MS.Internal.IO.Zip.ZipIOBlockManager.Dispose(Boolean disposing)
at MS.Internal.IO.Zip.ZipIOBlockManager.Dispose()
at MS.Internal.IO.Zip.ZipArchive.Dispose(Boolean disposing)
at System.IO.Packaging.ZipPackage.Dispose(Boolean disposing)
at System.IO.Packaging.Package.System.IDisposable.Dispose()
at Inedo.ProGet.Service.IndexedFeed.UpdatePackage(PackageStorePackage storePackage)
at Inedo.ProGet.Service.IndexedFeed.<>c__DisplayClassa.<RebuildIndex>b__7(PackageStorePackage storePackage)

From what I can tell it looks fine. I was able to unzip it. That would leave me to believe that somehow they are locked and proget can’t open them .I’ve searched for open handles, but I don’t see any of them open.

[Alex]

Based on the error message and symptoms (it was working fine, until it wasn't), it would appear that the indexing error is from a poison package.

We made the mistake of using Microsoft’s Packaging libraries (System.IO.Packaging) to open this package, and among many other bugs, it will produce an un-catchable exception (fun fact: if you happened to be on a non-english Locale, it will terminate the whole process with a stack overflow exception).

We cannot work around this problem, but the bug appears to be fixed in .NET 4.5.1. If you upgrade to that, the error should go away.