Failure - PayloadTooLarge about gcsf

[harababurel]

Most likely happens because of the way GCSF requests chunks of the file tree. It sends a long query of the form "d_1" in parents or "d_2" in parents or ... or "d_k" in parents, where d_1, d_2, ..., d_k are all directories on a given level. I can imagine this type of query exceeds some fixed limit enforced by Drive, especially in the case of very populated accounts.

I'm looking into how I can improve the mount process as described in #4. Requesting all files at once and processing/rearranging them locally would most likely improve the mount time and fix this issue as well.

[AndreiBarsan]

Amazing work on this project!

But, sadly, I also get this error when I try to mount. :(
For what it's worth, I have a lot of stuff on my (now, nearly 10 year old) Drive... This includes weird stuff like some datasets which may have huge numbers of subdirectories, etc.

[harababurel]

I have changed the mount mechanism as of version 0.1.17 (ad5d8bb). The file system now requests all files at once (well, in chunks of as many as the API can provide) and rearrange them in the correct hierarchy afterwards. This should fix the PayloadTooLarge error and likely improve the mount time, unless you have a lot of files which are shared with you.

Consider giving this version a try and let me know if it improves your experience.

[Deadolus]

Thank you for looking in to this.
Indeed I now no longer receive that error.
You may underestimate the amount of stuff some people have on their Google drives (me included).
I will create another ticket to describe my problem.
Thank you very much for fixing this issue - keep up the good work.