关于“運用 AlloyDB 和 Vertex AI 建構 LLM 和 RAG 型對話應用程式”的评价
评论
Pavan K. · 评论28 minutes之前
Cymbal Air wasn't able to answer certain questions
Zaynab R. · 评论2 小時之前
Pravin S. · 评论2 小時之前
Carlos G. · 评论2 小時之前
Raja K. · 评论2 小時之前
Siddharth V. · 评论2 小時之前
Sudhanshu K. · 评论4 小時之前
Michael S. · 评论4 小時之前
Umer F. · 评论4 小時之前
Anahita F. · 评论5 小時之前
Phil H. · 评论5 小時之前
Gabriel G. · 评论6 小時之前
Ameya G. · 评论10 小時之前
Ameya G. · 评论11 小時之前
Jun Qun T. · 评论12 小時之前
Swetha R. · 评论13 小時之前
files did not copy
David F. · 评论13 小時之前
Jansee K. · 评论14 小時之前
Arsalan K. · 评论20 小時之前
Leonard H. · 评论1 day之前
Error 255 during ssh access...
Andrea F. · 评论1 day之前
The AI app at the end did not work, it could not find me any flights at all.
Ethan P. · 评论1 day之前
errors while deploying toolbox container, first it was: "(.venv) student-00-15a64b9036b1@app-vm:~$ gcloud run deploy toolbox --image $IMAGE --service-account toolbox-identity --region $REGION --set-secrets "/app/tools.yaml=tools:latest" --args="--tools-file=/app/tools.yaml","--address=0.0.0.0","--port=8080" --network default --subnet default --no-allow-unauthenticated --quiet Deploying container to Cloud Run service [toolbox] in project [qwiklabs-gcp-04-ce4a077bd699] region [us-west1] Deploying... Setting IAM Policy...warning Creating Revision...failed Deployment failed Setting IAM policy failed, try "gcloud beta run services remove-iam-policy-binding --region=us-west1 --member=allUsers --role=roles/run.invoker toolbox" ERROR: (gcloud.run.deploy) spec.template.spec.volumes[0].secret.items[0].key: Permission denied on secret: projects/179808091555/secrets/tools/versions/latest for Revision service account toolbox-identity@qwiklabs-gcp-04-ce4a077bd699.iam.gserviceaccount.com. The service account used must be granted the 'Secret Manager Secret Accessor' role (roles/secretmanager.secretAccessor) at the secret, project or higher level. spec.template.spec.volumes[1].secret.items[0].key: Permission denied on secret: projects/179808091555/secrets/tools/versions/latest for Revision service account toolbox-identity@qwiklabs-gcp-04-ce4a077bd699.iam.gserviceaccount.com. The service account used must be granted the 'Secret Manager Secret Accessor' role (roles/secretmanager.secretAccessor) at the secret, project or higher level." ------- I granted toolbox-identity@qwiklabs-gcp-04-ce4a077bd699.iam.gserviceaccount.com Secret Manager Secret Accessor role then container fails to start with ------- "(.venv) student-00-15a64b9036b1@app-vm:~$ gcloud run deploy toolbox --image $IMAGE --service-account toolbox-identity --region $REGION --set-secrets "/app/tools.yaml=tools:latest" --args="--tools-file=/app/tools.yaml","--address=0.0.0.0","--port=8080" --network default --subnet default --no-allow-unauthenticated --quiet Deploying container to Cloud Run service [toolbox] in project [qwiklabs-gcp-04-ce4a077bd699] region [us-west1] Deploying... Setting IAM Policy...warning Creating Revision...failed Deployment failed Setting IAM policy failed, try "gcloud beta run services remove-iam-policy-binding --region=us-west1 --member=allUsers --role=roles/run.invoker toolbox" ERROR: (gcloud.run.deploy) The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable within the allocated timeout. This can happen when the container port is misconfigured or if the timeout is too short. The health check timeout can be extended. Logs for this revision might contain more information. Logs URL: https://console.cloud.google.com/logs/viewer?project=qwiklabs-gcp-04-ce4a077bd699&resource=cloud_run_revision/service_name/toolbox/revision_name/toolbox-00006-86l&advancedFilter=resource.type%3D%22cloud_run_revision%22%0Aresource.labels.service_name%3D%22toolbox%22%0Aresource.labels.revision_name%3D%22toolbox-00006-86l%22 For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start"
Alexander M. · 评论1 day之前
Cody H. · 评论1 day之前
Rishi S. · 评论1 day之前
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。