Martino Trevisan
Martino Trevisan
Ciao, It depends mainly on your disk... we tested with 10-12Gbps... But we had several raid0 ssd disks...
try with windows
done grazie
Guys I cannot reproduce the error. It is working fine on my Ubuntu and MacOS PCs. Do you have any special configuration of Chrome?
This is not related to this tool. You should see the documentation of the [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol). However, you could get the body of a HTTP response using: [Network.getResponseBody](https://chromedevtools.github.io/devtools-protocol/tot/Network#method-getResponseBody). You...
`Network.getResponseBody(reqid)` is wrong. reqid must not be passed as positional argument but as `requestId`. E.g. ``` Network.getResponseBody(requestId=reqid) ```
I've this problem too. I see a lot of file descriptors pointing to ~/.onedrive/entries.db
Update: Using debug feature i see a continuous flow of messages, like these ones. `[2015-05-03 12:18:46,990] DEBUG: worker0: got task: sy on "/home/homme/OneDrive/..."` `[2015-05-03 12:18:48,187] DEBUG: worker1: added task "sy"...
+1. I think is the biggest problem of onedrive-d. There is not relyability when using it.
I had this problem too. I had a set of files like this. archive.zip archive (homme).zip archive (homme) (homme).zip archive (homme) (homme) (homme).zip archive (homme) (homme) (homme) (homme).zip