-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[REGRESSION]: ArchiveFiles@2 w/ 7z-ultra compress the file in a format that ExtractFiles@1 can't open. #19918
Comments
This happened because of negligent reviews of #19842. |
Thanks, make sense. If they can upgrade to the latest 7z for both archiving and extracting, it will be the best solution. After they fix and merge this issue, do you know how long it takes to replicate the change so I can update my agents? |
Hi, thanks for the feedback! We are working on this |
Do we have an update on this issue? |
Can anyone confirm the issue is resolved? |
Hi @yuhungchun, |
@ismayilov-ismayil Thank you for the update. |
Just faced the same issue today (for some reason the pipeline ran successfully until yesterday). Yesterday (Successful)Initialize First Job:
Archive (using task version 2.231.1 and 7-Zip 19.00)
Initialize Second Job:
Extract Files (using task version 1.231.1 and 7-Zip version 16.02)
Today (Error during extract)Initialize First Job
Archive (using task version 2.244.1 and 7-Zip version 23.01)
Initialize Second Job
Extract (with error - using task version 1.231.1 and 7-Zip 16.02)
|
Even though 7Zip was upgrade to v23 in ExtractFilesV1 task version 1.245.1 in #20339 I'm still getting version 16.02 during the pipeline execution. Coincidentally, it is the version available by default in the pipeline runner image: https://github.com/actions/runner-images/blob/ubuntu22/20240901.1/images/ubuntu/Ubuntu2204-Readme.md, which I was expecting to be ignored by the task considering there is a specific version being bundled with it. Looks like the lookup strategy is not consistent between ArchiveFiles and ExtractFiles causing the pipeline to hit the error above. |
Do we know if this issue is addressed now? Or people still seeing the same error? |
Any update on this Regression issue? |
The scenario I reported above was probably an edge case, that is not very obvious. After the update, Archive task would always use 23.03 (in Windows) while the Extract task in Linux would always fallback to 16.02. This would happen when using the |
Sound like for Extract task under Linux should be updated to use the same version as Windows if 7z format is used? |
PR: #20687 |
New issue checklist
Task name
ArchiveFilesV2
Breaking task version
231
Last working task version
229
Regression Description
We use heavily the ArchiveFiles@2 and ExtractFiles@1 and we found that since the version 231 ofr ArchiveFiles, the task ExtractFiles@1 is failing with the signature:
ERROR: Unsupported Method :
For binary files like dlls and exe files. Looks like the 7z tool is older now:
7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21
I found that if you upgrade to the 2024 version of 7-Zip, the extract works again.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 11
Relevant log output
Full task logs with system.debug enabled
UNSUCCESSFUL RUN
SUCCESSFUL RUN
Repro steps
No response
The text was updated successfully, but these errors were encountered: