Craig Alvord

@v-kellyluo I am not able to reproduce this issue on 1.35.0, on 20240925.3, or on a local build. I get the expected `RenameDestinationParentPathNotFound` error. Maybe you need to double-check your...

@v-kellyluo * Can you provide app logs, please? * Are you also able to remove yourself as owner? Does the problem reproduce when you do so? * Are you using...

@MRayermannMSFT Also agrees this is not a serious problem. The difference in error message could have something to do with whether OAuth or key is being used, in which case...

@v-kellyluo Can you verify that this is still reproducing?

@v-kellyluo We're still unable to repro on our end. Can you provide the VM you are using to test? Can you also answer the questions I asked above?

I am _still_ unable to reproduce, even on the VM.  > If don't use OAuth in both 1.35.0 and the current build, this issue only reproduces on current build....

@dwr-psandhu * How are you doing step 1? Are you able to successfully upload the symlinks using Storage Explorer? * Are you uploading to a standard blob container or an...

> Both source and destination are Storage v2 general purpose. So hierarchical namespaces is _not_ enabled, correct? > No error messages. Just the blob that represent symlinks are not copied...

@dwr-psandhu Correct, Storage Explorer is not using the `--preserve-symlinks` to copy. We will need to discuss the full implications of including this. We may just add an app setting to...

@dwr-psandhu Metadata is a different concept than symbolic links in this context. Can you clarify what you mean?