-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
GoogleError, Timeout in version 1.0.0 #128
Comments
Hi @janoshr, I just update the version of the I saw a potential fix for retry & timeout on their end. |
Unfortunately, the issue persists
|
You don't see this error anymore?
I think meanwhile you can use the old version before this one is fixed. |
I was running into the same thing and adding |
Hi @mijiapps, which version of |
@dalenguyen |
Thanks, I upgrade the package with |
@janoshr Same problem here. Have you managed to fix it? |
@bruno-machado I reverted back, not the best solution but it works for now |
@janoshr What version? V0.30? |
@bruno-machado v0.10.0 |
Still happen in version v1.35, how I can fix that? |
Also getting the same error on v1.35. It's related to collections data size, as specifying only one small collection to the "backups" function, instead of many big collections, solves the issue. Also, the issue doesn't occur when running the same function locally using functions-framework. Tried to add "google-gax" to package.json, but the error still triggers. Anyone else made some progress on this? @yamauchieduardo @dalenguyen ? |
@DavenMartel Could you please provide:
|
Sure, it works just fine on:
But won't run once the function has been deployed on:
Also, the error only happens when trying to run the export, not when the app gets initialized. |
Thanks, @DavenMartel. I will check it this weekend. |
Hi @DavenMartel, your zip file contains service_account file. I deleted the link from your comment. However, you should disable that service account ASAP. |
Hi @DavenMartel, just tried, and it's working for me. Deploy script
Dependencies
|
@dalenguyen Thanks a lot for the heads up and removal, I swapped the file just after uploading it, but didn't realize it stayed in history. We've rotated credentials and thankfully, this wasn't prod data. As for the issue here, I ended up allowing more CPU and memory ressources to the associated Cloud Run container, and that solved it for me. I've seen in other threads that it might be related to ECONNRESET and/or unhandled promises, but I haven't found a clear solution. |
I'm glad that you solved this issue 🙌 |
Hey. it looks like I face the same timeout issue. I'm running the code from the Cloud Build pipeline with 32 CPU and 32 GB RAM, so that's definitely not a resources-related issue. I'm using the latest version of the library, but I'm trying to backup a pretty big collection. |
I had an older version of this package, v0.10.0, I made a backup (took a couple of hours but worked, the database is quite large) I upgraded to v1.0.0 and I got the following errors:
I ran it two times the following was the first error that I got
Then I reverted back to the older version v0.10.0 and it works fine again.
I used the same node version and everything the only thing that was changed is the package version.
The text was updated successfully, but these errors were encountered: