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

Version of 7z.exe must be v9.XX #34

Closed
warlord0 opened this issue Dec 5, 2016 · 3 comments
Closed

Version of 7z.exe must be v9.XX #34

warlord0 opened this issue Dec 5, 2016 · 3 comments
Assignees
Labels

Comments

@warlord0
Copy link

warlord0 commented Dec 5, 2016

I spent a few hours wondering why this worked just fine on my Linux system but failed on Windows.

On windows it returned no files having been extracted even though when I looked at the output folder there they were.

Turned out I have 7z.exe v16.04 on the windows machine. The v15.XX and up do not report their progress to stdout like v9.XX as "Extracting " so the 7z succeeds, but node-7z module is unable to capture the list of extracting files from stdout.

Not really an error as such, but thought it may be worth adding into the readme.

@q2s2t q2s2t added the bug label Mar 5, 2017
@q2s2t
Copy link
Owner

q2s2t commented Mar 5, 2017

hi,
i don't have a windows machine available right now. could you copy-paste the outputs of your extraction using v9.XX and v>=15.XX ?

@MichaelFroeschen
Copy link

MichaelFroeschen commented Dec 1, 2017

The switch -bb1 has to be set in order for the progress to work.
Without the switch, 7-Zip shows a single line in the cli, that updates itself based on the current progress.
With the switch, every processed file is shown.

From the changelog:

15.05 beta 2015-06-14
(...)
-Console version now shows names of processed files only in progress line by default.
-new -bb[0-3] switch to set output log level. -bb1 shows names of processed files in log.

The output also changed, so that it no longer displays
Extracting some/file/path
but
- some/file/path

@q2s2t
Copy link
Owner

q2s2t commented Dec 5, 2018

Closed in v1.0.0
Check the README to adapt your code to the new API

@q2s2t q2s2t closed this as completed Dec 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants