Extracting Text from the Images using the Google Cloud Vision API Reviews
4517 reviews
Ayman B. · Reviewed около 1 года ago
Task4.1 appears to be the gating step to successful lab execution.
h t. · Reviewed около 1 года ago
Kevin Q. · Reviewed около 1 года ago
Amirkhan I. · Reviewed около 1 года ago
Fagner T. · Reviewed около 1 года ago
the service account does not exist, please check with the lab's existing service accounts
Kamurasi J. · Reviewed около 1 года ago
Gavriel D. · Reviewed около 1 года ago
A good lab, however the instructions with the appspot service account IAM were unclear
Kinga K. · Reviewed около 1 года ago
Rajeev R. · Reviewed около 1 года ago
Devalin D. · Reviewed около 1 года ago
The lesson assumes the app engine has already been created when you try to add the iam policy binding. But I had to create it then grant the Artifact Registry Reader Role to the Service Account. I would strongly recommend telling people to open a txt file or notepad so that they can keep track of all the commands that they'll have to edit. I also recommend removing the capitalized letters where buckets, and pubsub topics are called for. People will instinctively copy and paste what's there and the console will throw an error for formatting.
Gabriel H. · Reviewed около 1 года ago
JUNE D. · Reviewed около 1 года ago
Jeremiah A. · Reviewed около 1 года ago
very difficult lab work The code does not work I was unable to complete it unfortunately
Ievhen S. · Reviewed около 1 года ago
Commands for Task 4 do not work
JUNE D. · Reviewed около 1 года ago
Task 4. Deploy the functions - Do Not Work student_04_aaca86bb7146@cloudshell:~ (qwiklabs-gcp-01-dcdf604e7b83)$ gcloud projects add-iam-policy-binding qwiklabs-gcp-01-dcdf604e7b83 \ --member="serviceAccount:qwiklabs-gcp-01-dcdf604e7b83@appspot.gserviceaccount.com" \ --role="roles/artifactregistry.reader" ERROR: Policy modification failed. For a binding with condition, run "gcloud alpha iam policies lint-condition" to identify issues in condition. ERROR: (gcloud.projects.add-iam-policy-binding) INVALID_ARGUMENT: Service account qwiklabs-gcp-01-dcdf604e7b83@appspot.gserviceaccount.com does not exist. (qwiklabs-gcp-01-dcdf604e7b83)$ gcloud functions deploy ocr-extract --runtime python39 --trigger-bucket image_bucket_qwiklabs-gcp-01-dcdf604e7b83 --entry-point process_image --set-env-vars "^:^GCP_PROJECT= qwiklabs-gcp-01-dcdf604e7b83:TRANSLATE_TOPIC=translate_topic_qwiklabs-gcp-01-dcdf604e7b83:RESULT_TOPIC=result_topic_qwiklabs-gcp-01-dcdf604e7b83:TO_LANG=es,en,fr,ja" In a future Cloud SDK release, new functions will be deployed as 2nd gen functions by default. This is equivalent to currently deploying new with the --gen2 flag. Existing 1st gen functions will not be impacted and will continue to deploy as 1st gen functions. You can preview this behavior in beta. Alternatively, you can disable this behavior by explicitly specifying the --no-gen2 flag or by setting the functions/gen2 config property to 'off'. To learn more about the differences between 1st gen and 2nd gen functions, visit: https://cloud.google.com/functions/docs/concepts/version-comparison ERROR: (gcloud.functions.deploy) Failed to upload the function source code to signed url: https://storage.googleapis.com/uploads-353051714080.us-central1.cloudfunctions.appspot.com/66b315c1-b658-4666-af0f-f82638919648.zip?GoogleAccessId=service-892274846650@gcf-admin-robot.iam.gserviceaccount.com&Expires=1725807866&Signature=nJo0ANi33GcZvJZeB%2F9wP3tF8JzuzOW%2BES9VkjJSlJxrmoNFA6hr4CxN6xgDkltUffMfjThQNEXGOvErqdyBw92h174%2FrmD%2FSJC8FXN74n8fPiVtu6P0i2r9MZaSCzqAg780cLUaRfCZHGY7AHTdNx9xA6lUVRi7wS3QWKo%2BQi6fAsCOB3Yc6Z%2FROZ2Wu8IvnaKzQTI4rG6pbm8T%2FF4U%2B0qSWF%2BzSPu%2FSMsA8xjkGnMNzAw1zUxy9IKu2PxoV%2Faxkbq7dVHaCX0UhLSAfMUePTf1w8mNXh%2BPx4NYumd%2By7SSpszJu59ul0lqRMmums7oMdBB6Xs0%2F27CUm60TdT5ag%3D%3D. Status: [400:b"<?xml version='1.0' encoding='UTF-8'?><Error><Code>EntityTooLarge</Code><Message>Your proposed upload is larger than the maximum object size specified in your Policy Document.</Message><Details>Content-length exceeds upper bound on range</Details></Error>"]
JUNE D. · Reviewed около 1 года ago
difficult lab work the code didn't work for some reason couldn't pass the first time
Ievhen S. · Reviewed около 1 года ago
Manju Vallabha P. · Reviewed около 1 года ago
The steps can be evolved to set environment variables in the shell such that the user doesn't need to edit commands inline. It would make the lab go much faster. Also the default app engine service account did not exist so the first cloud function deployment throws an error.
Prateek S. · Reviewed около 1 года ago
The end does not work. Please check this problem.
Daniel C. · Reviewed около 1 года ago
Ievhen S. · Reviewed около 1 года ago
Uzor N. · Reviewed около 1 года ago
Daniel C. · Reviewed около 1 года ago
ERROR: Policy modification failed. For a binding with condition, run "gcloud alpha iam policies lint-condition" to identify issues in condition. ERROR: (gcloud.projects.add-iam-policy-binding) INVALID_ARGUMENT: Service account qwiklabs-gcp-04-ff7bb8ba9a34@appspot.gserviceaccount.com does not exist.
Mohit T. · Reviewed около 1 года ago
could not add aim access due to no cloud function activate. Required to Enable the App Engine Default Service Account If you do not see the appspot service account in the list, it means the App Engine service account has not been created. To create it, you need to enable the App Engine service in your project: gcloud app create --project=qwiklabs-gcp-00-fc4a556c3851
Daniel S. · Reviewed около 1 года ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.