关于“使用 ADK 和 Agent2Agent (A2A) SDK 连接远程智能体”的评价
8159 条评价
Yuvraj S. · 已于 21 days前审核
Nazrana H. · 已于 21 days前审核
Ashmit G. · 已于 21 days前审核
Tammana A. · 已于 21 days前审核
Sneha M. · 已于 21 days前审核
Santosh R. · 已于 21 days前审核
Rohit C. · 已于 21 days前审核
Sanobar S. · 已于 21 days前审核
Komal P. · 已于 21 days前审核
RAMESH A. · 已于 21 days前审核
Rohith B. · 已于 21 days前审核
Preet J. · 已于 21 days前审核
Kaviyarasu P. · 已于 21 days前审核
Eishaan K. · 已于 21 days前审核
Saikrishna V. · 已于 21 days前审核
Kanika B. · 已于 21 days前审核
ᎪຮᏂυtoຮᏂ B. · 已于 21 days前审核
Monisha K. · 已于 21 days前审核
I'm very satisfied by doing this lab
Avadhut G. · 已于 21 days前审核
the agent.json no such file or directory is found
Mithra G. · 已于 21 days前审核
Priya .. · 已于 21 days前审核
I followed the lab instructions exactly for the Cloud Run A2A deployment step, including using the exact command, project ID, region (`us-east4`), service name (`illustration-agent`), and `--a2a` flag as shown in the lab. The deployment completed successfully multiple times, and Cloud Run confirmed that the service was deployed and serving 100% traffic. However, the lab validator still did not mark the task as complete. On further verification, the deployed service URL was live, but the expected A2A discovery endpoint returned: `{"detail":"Not Found"}` This suggests the issue may be with the lab validation logic, hidden project scaffold/configuration, or an undocumented requirement in the provided starter files rather than the deployment command itself. Because of this, I was unable to complete the lab despite reaching the final deployment stage successfully. Please review the validator and/or provide clearer instructions on the exact expected A2A agent export/discovery setup.
Zahurafzal M. · 已于 21 days前审核
time is so less
Dhwnit S. · 已于 21 days前审核
nice
Parminder K. · 已于 21 days前审核
Mahesh p. · 已于 21 days前审核
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。