-
Notifications
You must be signed in to change notification settings - Fork 47
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
Intermittent failure in all googledrive functions #279
Comments
Sounds related to #277 I am beginning to suspect that something has changed on the backend (Google side) re: the timescale of "eventual consistency". |
It seems like the issue has actually gotten worse over the past days/weeks. I've tried to run drive_mkdir() a dozen times with no success within a function where it at least occasionally worked last week. Is it possible that this is account-related to some degree? |
What error do you see with But my years of wrapping Google APIs definitely confirms that certain APIs seem to go through "troubled periods" that are never acknowledged publicly and often just clear up on their own. I assume it means there is some challenge in the back end systems, that probably cause lots of downstream infelicities, and it doesn't really get identified as a specific problem with individual products. |
The inclusion of |
I am experiencing what seems like a related issue. Calls to several googledrive functions, including The example below includes four identical calls to |
May or may not be related: For me the errors began appearing immediately after I upgraded OS X on my MacBook Pro to v. Catalina. After the OS upgrade, googledrive began requiring reauthorization of credentials to execute operations on Google Drive, multiple times in succession. It also started throwing the "Error in add_id_path()" errors that @JMKelleher and other's have noted, as well as getting stuck in I/O land. Shortly after this, I updated googledrive to v. 1.0.0. This update did not resolve the various errors I was experiencing with googledrive functions. My guess (it is only a guess): the various errors people are experiencing have something to do with authorizations. Specifically, they may have something to do with the switch under googledrive v 1.0.0 to using gargle to handle Auth functionality. Update: This morning my code ran fine, without any glitches from |
Similar issues I think - #281 (comment) |
I have experienced the error earlier today related to |
I am experiencing a similar issue with drive_ls. The code previously worked last in November.
I get the following error message:
Where I also attempted to use This issue occurs on Windows and Mac. My
|
As an update to my message above, the following is a valid workaround but I needed to traverse the nested directory structure to find the right object id, |
As I use
|
I still have yet to experience this phenomenon or get enough data to truly study it. But I have formed an untestable hypothesis about the root cause and installed a fix 🤞 Needless to say, please open a new issue if you update to this dev version and still see the phenomenon. |
Just in case in anyone still looking for an answer, I was facing the same issue as well. I just updated my R version to the latest version 3.6.3 and it resolved this issue. |
When using any googledrive function (downloading, uploading, sharing, etc.) I will intermittently receive the following error:
This occurs anywhere for 25% to 80% of the time, and will eventually work after running the function multiple times. It appears to occur more frequently after running several commands in quick succession, e.g. in a function making multiple calls to the same folder. I've attached an example with drive_ls, though it is not particularly informative. For context- this is a shared drive folder owned by me in my home directory containing several other shared folders. No other folders in any directory have the same name.
Unsure how to provide a reprex in this case as it appears that this issue is not occurring for most people, but would be happy to provide one if given instruction.
The text was updated successfully, but these errors were encountered: