BadRequest on Google Doc files about gcsf

[avindra]

Started getting this recently as well. Any clues yet?

Is this the same as #34 also?

[harababurel]

Since 88ee06b (included in 0.1.24), special Drive files which cannot be exported are represented as dummy text files containing a message similar to:

UNEXPORTABLE_FILE: The MIME type of this file is "application/vnd.google-apps.map", which can not be exported from Drive. Web content link provided by Drive: None

which should get rid of the BadRequest errors. I have so far only found Maps and Forms to fit in this category, but will add others if anyone reports them. Other special files (Sites and Drawings) can be exported and are now supported by GCSF.

#34 is a different issue altogether, caused by a mix of:

• having >100 GB of data on Drive; note that only the file count influences the mount time, not the file size
• the design decision to make GCSF fetch everything at mount time instead of being lazy and fetching as needed
• Drive API allowing callers to request between 100 and 1000 files per page (see the pageSize parameter) but providing no guarantee on how many files it will actually return (only 460/page in this case).
• the likelihood of a user having a significant number of files shared with them, which can't be easily excluded from the API response (see Google Drive API files setq sharedWithMe=false causes “500 Internal Server Error” on stack overflow). The workaround described in the comments is not a viable option -- for instance I am the owner of some files within a large shared directory owned by someone else. These files match 'me' in owners but they do not belong to my drive, which means that using this workaround by itself makes a bunch of unrelated files suddenly lose their hierarchical order and appear flattened in the mount directory.

Solving #34 requires a bit more work and possibly a redesign of the file system.