We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Apologies if this is a duplicate, but I couldn't find another report for this.
10.22.1
macOS
azcopy cp "<vhd_uri>" .
As indicated by the command, a log file is created. However, the log file is actually missing the .log file extension indicated by the output.
.log
Log file is located at: /Users/<user>/.azcopy/<uuid>.log
However, the file is actually at /Users/<user>/.azcopy/<uuid>
/Users/<user>/.azcopy/<uuid>
Run azcopy cp <uri> .
azcopy cp <uri> .
Observe that the log file is not created with the correct extension
The file is created at the expected directory, and can be used as expected.
The text was updated successfully, but these errors were encountered:
@nakulkar-msft can you please take a look?
Sorry, something went wrong.
Closing this issue as a PR was merged that will be released as part of 10.23.0 which will resolve this issue.
nakulkar-msft
Successfully merging a pull request may close this issue.
Apologies if this is a duplicate, but I couldn't find another report for this.
Which version of the AzCopy was used?
10.22.1
Which platform are you using? (ex: Windows, Mac, Linux)
macOS
What command did you run?
azcopy cp "<vhd_uri>" .
What problem was encountered?
As indicated by the command, a log file is created. However, the log file is actually missing the
.log
file extension indicated by the output.Log file is located at: /Users/<user>/.azcopy/<uuid>.log
However, the file is actually at
/Users/<user>/.azcopy/<uuid>
How can we reproduce the problem in the simplest way?
Run
azcopy cp <uri> .
Observe that the log file is not created with the correct extension
Have you found a mitigation/solution?
The file is created at the expected directory, and can be used as expected.
The text was updated successfully, but these errors were encountered: