关于“Integrate Cloud Run Functions with Firestore”的评价

Kripesh K. · 已于 about 1 month前审核

Muhammad Zunnurain H. · 已于 about 1 month前审核

Oskar Ś. · 已于 about 1 month前审核

Leonel N. · 已于 about 1 month前审核

This part was incorrect, had to fix the code myself: ``` Write the function code In the editor, add the following code below in the firestore_functions/index.js file: ```

Mitchell T. · 已于 about 1 month前审核

Sanjay R. · 已于 about 1 month前审核

Liquan Y. · 已于 about 1 month前审核

Mayur K. · 已于 about 1 month前审核

Mayur K. · 已于 about 1 month前审核

Eric T. · 已于 about 1 month前审核

Sajja V. · 已于 about 1 month前审核

When creating functions error is thrown, although the function is created successfully upon retry, it is still reducing points in the progress leading to incompletion : ERROR: (gcloud.functions.deploy) OperationError: code=3, message=Could not create or update Cloud Run service newcustomer, Container Healthcheck failed. Quota exceeded for total allowable memory per project per region.

Santhosh N. · 已于 about 1 month前审核

This lab is not working as expected please check this one

Srinivas A. · 已于 about 1 month前审核

Madhu K. · 已于 about 1 month前审核

Bhuvan Krishna S. · 已于 about 1 month前审核

2nd to last task never fully credited me even though i reviewed the configuration and it was exactly as described in the lab. It also functioned correctly, adding the fullname field so not clear what acceptance criteria it is using. 2nd attempt the lastname piece worked fine. Then the last steps of reading a secret failed. Even though I correctly confirmed the IAM setup and that the secret was save. It complained when deploying the updated function that is could not find the key. I waited for significant amount time but it seems like the overall platform is flaky. third time a charm, went through

Cory R. · 已于 about 1 month前审核

2nd to last task never fully credited me even though i reviewed the configuration and it was exactly as described in the lab. It also functioned correctly, adding the fullname field so not clear what acceptance criteria it is using. 2nd attempt the lastname piece worked fine. Then the last steps of reading a secret failed. Even though I correctly confirmed the IAM setup and that the secret was save. It complained when deploying the updated function that is could not find the key. I waited for significant amount time but it seems like the overall platform is flakey.

Cory R. · 已于 about 1 month前审核

2nd to last task never fully credited me even though i reviewed the configuration and it was exactly as described in the lab. It also functioned correctly, adding the fullname field so not clear what acceptance criteria it is using.

Cory R. · 已于 about 1 month前审核

Ana G. · 已于 about 1 month前审核

Madhu K. · 已于 about 1 month前审核

Mujahedul I. · 已于 about 1 month前审核

Rayane J. · 已于 about 1 month前审核

Andrew G. · 已于 about 1 month前审核

great

Gurpreet K. · 已于 about 1 month前审核

Areyci H. · 已于 about 1 month前审核