Replies: 1 comment
-
Tried to set the NUGET_PACKAGE_EXTRACTION_USE_MMAP environment variable to 0 in my GitHub action. It did not change the problem - still being corrupted when unpacked after pull, but the stack trace changed:
Now it goes through So this indicates to me that either the problem is server side at GitHub when extracting the transferred package or in the PushCommand when pushing to GitHub package repository. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a problem with a nuget package that I push to a NuGet repository hosted on GitHub in my organization.
When pushed, I consume it in another project, but when I get the package down, it is corrupted. At a glance, it looks correct, has same size, but the contents differ completely from the original package content.
The nuget package is a multi-target framework containing a
net48
and anet6.0-windows7.0
version of the same dll. After pushing to GitHub repository and then pulling it, thenet6.0-windows7.0
version is identical with the version from the package before push. But thenet48
version is completely different - although they look the same size.Also, I noticed this in a log from dotnet restore with diagnostic verbosity:
Is it correct that it should go into
System.IO.Compression.DeflateStream
?Beta Was this translation helpful? Give feedback.
All reactions