Add known-issues.md (#877)

* Add known-issues.md for known issues and application 'quirks'
This commit is contained in:
abraunegg 2020-04-20 12:37:19 +10:00 committed by GitHub
parent f9ea31476f
commit 183567eba6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 37 additions and 0 deletions

View file

@ -44,3 +44,6 @@ If you encounter any bugs you can report them here on Github. Before filing an i
2. Fill in a new bug report using the [issue template](https://github.com/abraunegg/onedrive/issues/new?template=bug_report.md)
3. Generate a debug log for support using the following [process](https://github.com/abraunegg/onedrive/wiki/Generate-debug-log-for-support)
4. Upload the debug log to [pastebin](https://pastebin.com/) or archive and email to support@mynas.com.au
## Known issues
See [docs/known-issues.md](https://github.com/abraunegg/onedrive/blob/master/docs/known-issues.md)

34
docs/known-issues.md Normal file
View file

@ -0,0 +1,34 @@
# Known Issues
The below are known issues with this client:
## Unable to recursively delete directories in OneDrive Business when Retention Policy is enabled
**Issue Tracker:** https://github.com/abraunegg/onedrive/issues/338
**Description:**
Some organisations enable a retention policy on OneDrive Business that prevents the recursive deletion of data. The client is unable to delete directories as requested.
**Workaround:**
Client will print the following when this issue is encountered:
```
ERROR: Unable to delete the requested remote path from OneDrive: <dir>
ERROR: This error is due to OneDrive Business Retention Policy being applied
WORKAROUND: Manually delete all files and folders from the above path as per Business Retention Policy
```
A future version of onedrive will attempt to resolve this automatically negating the need for the above message.
## Moving files into different folders should not cause data to delete and be re-uploaded
**Issue Tracker:** https://github.com/abraunegg/onedrive/issues/876
**Description:**
When running the client in standalone mode (`--synchronize`) moving folders that are sucessfully synced around between subseqant standalone syncs causes a deletion & re-upload of data to occur.
**Explanation:**
Technically, the client is 'working' correctly, as, when moving files, you are 'deleting' them from the current location, but copying them to the 'new location'. As the client is running in standalone sync mode, there is no way to track what OS operations have been done when the client is not running - thus, this is why the 'delete and upload' is occurring.
**Workaround:**
If the tracking of moving data to new local directories is requried, it is better to run the client in service mode (`--monitor`) rather than in standalone mode, as the 'move' of files can then be handled at the point when it occurs, so that the data is moved to the new location on OneDrive without the need to be deleted and re-uploaded.