Changed the zip dependency from 'unzip' to 'node-unzip-2' #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…longer zip urls without error.
|
Thanks for fixing this @WillWhiteneck! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've noticed that node-odm will throw an error for certain zip-urls, like this one:
https://firebasestorage.googleapis.com/v0/b/friendly-pix-776bf.appspot.com/o/LbD76QM7duhWtxaZbjTGnje4E6n1%2Fzips%2F1529195220007%2Fmyzipfile.zip?alt=media&token=1190c978-3fd0-4304-a07f-89c1e59e28a1
The error that gets returned says "invalid stored block lengths." I was able to get around this by upgrading the "unzip" dependency to "node-unzip-2." The underlying issue is discussed here: EvanOxfeld/node-unzip#40