-
Notifications
You must be signed in to change notification settings - Fork 917
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
Functions don't deploy and throw "@google-cloud/storage" error #1222
Comments
It used to deploy fine till yesterday and suddenly my pipelines start failing with deployment errors today. Could you guys help me out? |
There are issues with cloud storage currently, which is what is causing your deploy errors. The team is working on it and hopefully these will be resolved soon. |
Maybe it's a thing to update your 'status.firebase.google.com' webpage... Or give an insight in when you think this is fixed? @thechenky |
Not sure if this is the place to put this, but we are experiencing a similar problem. Only started failing this morning.
The problem appears to be with BigQuery here rather than Cloud Storage. Not sure if they are linked though? Reverting to a earlier commit that was working and re-deploying still gives the above error |
Now i'm experiencing a new error: node_modules/gaxios/build/src/index.d.ts(14,66): error TS1005: '>' expected. |
We're seeing the same today, we haven't changed any packages and finding others on stackoverflow reporting the same https://stackoverflow.com/questions/55866695/read-document-in-firestore-from-firebase-oncall-cloud-function |
We're not going down the suggested root of node v8 until we get official confirmation this is fixed first #853 (I'm sorry, but I don't have time to debug a third-party intermittent environment issue which is also clearly effecting a lot of others in the same way) This issue has taken down our sales environment and is currently blocking us from deploying production. I don't see anything on cloud storage status. I have no idea how to get our sales-env functions back up. Can you provide a workaround or more details please @thechenky |
I also agree with @willemjanvankranenburg , I'm tired of finding known firebase issues in github/stackoverflow/firebase slack community after our CI and deployments fail. We've got firebase statuses streaming into our slack development channel for exactly this reason. |
Hi @ahaverty I'm sorry for the frustration this is causing. It is our policy (Cloud and Firebase) to post on the dashboard when >10% of customers are affected, and this was below that threshold. |
We've had 45 out of 149 functions throw an error like this on our last deploy. Side note: |
I used the response from https://stackoverflow.com/questions/55866695/read-document-in-firestore-from-firebase-oncall-cloud-function . I set my engine to node: 8 in package.json its working |
NodeJS 6 deployments seem to be back to normal for us this morning @JainamJhaveri (No changes made on our side) |
Great to hear issues are resolved! And yes, I would recommend setting Node version to 8 (in your package.json) since Node 6 has been announced deprecated by the Google Cloud Functions team. I've also raised the frustrations many of you voiced about issues not being posted to the dashboard and will follow up on any updates on that if we have them (as I've said, posting thresholds are mandated by Cloud and Firebase policy but I think it's important that community feedback is heard). Thanks again for everyone's patience!! Closing this out now. If you encounter any other issues please don't hesitate to open another bug. |
I am getting the same error. Could anyone please let me know how to overcome this error ASAP. |
[REQUIRED] Environment info
firebase-tools: 6.7.1
Platform: macOS
[REQUIRED] Test case
Check my project's package.json below:
[REQUIRED] Steps to reproduce
firebase deploy --only functions
[REQUIRED] Expected behavior
Functions should deploy without any error as they used to be earlier
[REQUIRED] Actual behavior
Functions don't deploy and throw "@google-cloud/storage" error for all functions
The text was updated successfully, but these errors were encountered: