-
-
Notifications
You must be signed in to change notification settings - Fork 65
-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
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
.mignore file causes sync error due to new Dropbox business folder structure #999
Comments
Thanks for the report! Darn it, this sounds like it will be a bit of a pain to adapt to. Are all of the sub-folders still synching correctly in this new model? |
I think so. But I only installed maestral after the migration to the new (forced) folder structure, so it did a clean sync from scratch and all seems ok. I am having an issue where, after adding a fairly large amount of data all at once, maestral now is stuck on syncing, ie files are queued but no uploads are happening. However, I very much doubt this has anything to do with this issue. More likely some indexing issue, or maybe I ran into some API limits (no idea how to find out). |
This may well be API limits. You can check the logs for "backoff" of "ratelimit" messages after increasing the log level to DEBUG with |
No
However no syncing happens, it seems to make these API calls and wait for a response over and over again. Last night, I also tried a re-indexing. This morning I saw this message:
Presumably the same issue/some sort of timeout? I stopped/started the daemon again, then I get the above behaviour with the very many |
Describe the bug
Dropbox recently changed how folders are organised for business accounts. The top-level directory in the dropbox root directory is not writeable to the user any more, but instead contains sub-folders for the various groups you're a member of, and a folder with your full name as a "private" space.
Now, when I put the
.mignore
file in the top-level directory, I always get this error message in the maestral log:System:
Additional context
The text was updated successfully, but these errors were encountered: