-
Notifications
You must be signed in to change notification settings - Fork 118
error creating Google Drive client: gob: encoder: message too big #98
Comments
Interesting! Do you have a large number of files / folders in Drive? That error is occurring when skicka attempts to serialize the cache of metadata about the files stored in Drive and store it on disk. I reported this as a bug to the Go folks (golang/go#13850); we'll see what they say. It would be fairly straightforward to work around this in skicka, though it'd require changing the serialization format for the metadata, which would be nice to avoid if possible. So we'll see if a fix is imminent on the Go side, or if this is claimed to be working as intended (in which case we'll definitely fix it over here.) |
I checked with Go beta version (1.6.x), both in Mac and Windows and it still happen, guess it is not fix in Go side yet. Would be helpful if there are option to just push file to drive without syncing (force upload perhaps), I experience the case when skicka cost more time on update/serialize metadata than actual uploading. |
Serialize the file id to File struct map manually, rather than by passing it to gob/Encode() in its entirety, as the Encode() implementation recently changed to issue an error if the map is very large. (I believe that this will fix skicka issue #98.)
The fix just pushed should work-around the gloang issue from skicka. (Please let me know if it works!) I opened issue #99 to track the request to not track/update metadata. I'll start looking through the code to think about what this would entail. Thanks! |
Just checked, it is work like a champ on both MacOS and Windows Thanks! |
Today I experienced this issues while skicka try updating metadata cache, at some point it is stop and just spawn this message "error creating Google Drive client: gob: encoder: message too big"
This issues happen both in Windows and Mac, with go 1.5.2 installed.
Google around it seem internal issues of go and should be work around it for now.
The text was updated successfully, but these errors were encountered: