Análise de entidades e sentimento com a API Natural Language avaliações
187969 avaliações
Bilal M. · Revisado há over 1 year
Dilnaz S. · Revisado há over 1 year
Damir I. · Revisado há over 1 year
Sagar S. · Revisado há over 1 year
Mohsin A. · Revisado há over 1 year
Muhammad Ahmad M. · Revisado há over 1 year
Alansary E. · Revisado há over 1 year
sajitha S. · Revisado há over 1 year
Kyle K. · Revisado há over 1 year
Aman B. · Revisado há over 1 year
Dhrumit D. · Revisado há over 1 year
Reason for a 1-Star Rating for the Lab: Inconsistent API Behavior: The API key worked initially, but subsequent requests returned 403 "PERMISSION_DENIED" errors. The lab instructions do not clarify that API keys may not work for this request, leading to wasted time troubleshooting. Lack of Proper Documentation on Authentication: The lab should explicitly mention that Google Cloud APIs sometimes require OAuth authentication instead of API keys. A fallback authentication method (such as using gcloud auth application-default login) should be included in the instructions. Training Environment Issues: It’s unclear if rate limits, session restrictions, or other security policies are affecting the API key. The lab does not mention if temporary training accounts have API limitations, causing confusion. Time Wasted Due to Missing Context: Without a proper explanation of API authentication options, users are left to debug API errors instead of learning the intended concepts. Suggested Fixes: ✔ Clearly state in the lab that some APIs require OAuth authentication instead of an API key. ✔ Provide a troubleshooting section for common API issues, including "Method doesn't allow unregistered callers" errors. ✔ Mention Google Cloud's API quota restrictions for training environments and how to work around them.
Nicholas R. · Revisado há over 1 year
Reason for a 1-Star Rating for the Lab: Inconsistent API Behavior: The API key worked initially, but subsequent requests returned 403 "PERMISSION_DENIED" errors. The lab instructions do not clarify that API keys may not work for this request, leading to wasted time troubleshooting. Lack of Proper Documentation on Authentication: The lab should explicitly mention that Google Cloud APIs sometimes require OAuth authentication instead of API keys. A fallback authentication method (such as using gcloud auth application-default login) should be included in the instructions. Training Environment Issues: It’s unclear if rate limits, session restrictions, or other security policies are affecting the API key. The lab does not mention if temporary training accounts have API limitations, causing confusion. Time Wasted Due to Missing Context: Without a proper explanation of API authentication options, users are left to debug API errors instead of learning the intended concepts. Suggested Fixes: ✔ Clearly state in the lab that some APIs require OAuth authentication instead of an API key. ✔ Provide a troubleshooting section for common API issues, including "Method doesn't allow unregistered callers" errors. ✔ Mention Google Cloud's API quota restrictions for training environments and how to work around them.
Nicholas R. · Revisado há over 1 year
Sameer P. · Revisado há over 1 year
Rammohan D. · Revisado há over 1 year
たかおみ G. · Revisado há over 1 year
really great
Jason R. · Revisado há over 1 year
Shivam Y. · Revisado há over 1 year
Aaron T. · Revisado há over 1 year
Dhanvada, L. · Revisado há over 1 year
Peter F. · Revisado há over 1 year
Parth M. · Revisado há over 1 year
Vaibhav J. · Revisado há over 1 year
Gustavo N. · Revisado há over 1 year
Erdem A. · Revisado há over 1 year
Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.