-
Notifications
You must be signed in to change notification settings - Fork 219
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
All commands (including azcopy --version) takes ~8 seconds #2482
Labels
Comments
The issue seems to be in the version check. Running the following is near-instant: $ time azcopy --skip-version-check --version
azcopy version 10.22.0
real 0m0.017s
user 0m0.010s
sys 0m0.007s |
archlinux-github
pushed a commit
to archlinux/aur
that referenced
this issue
Dec 7, 2023
Also, apply patches for the following issues in 10.22.0: * Azure/azure-storage-azcopy#2483 * Azure/azure-storage-azcopy#2482 The second one by removing the version check entirely - I doubt many Arch Linux users are interested in such a feature, especially if it adds 8 seconds to every invocation.
Hi there! Thank you for bringing up this issue. I was able to repro this, and we are working on a fix. In the meantime, please use |
Hi! This has been fixed in our latest release. Please feel free to open a new issue in case you hit any other issues with AzCopy! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Arch Linux.
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?
There seems to be some kind of deadlock. Every command takes ~8 seconds. Also the stack trace.
See the attached strace.log.
How can we reproduce the problem in the simplest way?
Unsure.
Have you found a mitigation/solution?
Unfortunately, no.
The text was updated successfully, but these errors were encountered: