Closes #402 . Retry for reparse point error #403
Conversation
There was a problem hiding this comment.
Adding a while loop to retry registration does not look like an appropriate solution as it would just make the code to keep on looping indefinitely without letting the user to actually provide a way to update sync root directory.
I have tried several ways to reproduce the error 0x8007112A when registering a sync root but could not succeed. Can you share the steps to reproduce the issue? This would greatly help me analyse the issue further and suggest an appropriate fix.
|
@mayankchouhan1089 Just see #402 for repro |
The issue does not appear to be reproducible using the steps provided. For future cases, if you are able to reproduce the behavior, could you please share the output of the following command?
A likely cause could be that the placeholder may already have had a reparse tag. When Cloud Files discovers such a file, it attempts to add its own reparse tag; however, since the file already contains one, this results in error 0x8007112A. This is expected behaviour, and the error message is appropriate for this scenario. Given this, the changes proposed in the PR may not be necessary. |
4 participants
No description provided.