Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packages > 4GB fail to extract with SharpCompress #2811

Closed
MarkSiedle opened this issue Oct 7, 2016 · 5 comments
Closed

Packages > 4GB fail to extract with SharpCompress #2811

MarkSiedle opened this issue Oct 7, 2016 · 5 comments
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@MarkSiedle
Copy link

Packages that extract to a size greater than 4GB fail with error: "Unable to read beyond the end of the stream."

There appears to be a 4GB limit with SharpCompress. Need to investigate if there's a way for us to bypass this limitation (or maybe a flag we can set to bypass it?).

An example showing the error is attached.

To reproduce, I just made a text file > 4GB, zipped it, uploaded it as a package and tried to deploy.

ServerTasks-847.log.txt

Source: http://help.octopusdeploy.com/discussions/problems/47895

@MarkSiedle MarkSiedle added the kind/bug This issue represents a verified problem we are committed to solving label Oct 7, 2016
@droyad
Copy link
Contributor

droyad commented Jan 18, 2017

@droyad
Copy link
Contributor

droyad commented Jan 18, 2017

@markryd
Copy link

markryd commented Jan 19, 2017

4Gb requires zip64 support which SharpCompress doesn't have currently.

PR: adamhathcock/sharpcompress#205

@markryd markryd closed this as completed Jan 28, 2017
@octoreleasebot octoreleasebot added this to the 3.8.3 milestone Jan 28, 2017
@octoreleasebot
Copy link

Release Note: Add support for Nuget and Zip packages greater than 4Gb in size

@lock
Copy link

lock bot commented Nov 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot unassigned markryd Nov 25, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Nov 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

5 participants