Menghubungkan ke Agen Jarak Jauh dengan ADK dan SDK Agent2Agent (A2A) Ulasan

Yuvraj S. · Diulas 1 hari lalu

Nazrana H. · Diulas 1 hari lalu

Ashmit G. · Diulas 1 hari lalu

Tammana A. · Diulas 1 hari lalu

Sneha M. · Diulas 1 hari lalu

Santosh R. · Diulas 1 hari lalu

Rohit C. · Diulas 1 hari lalu

Sanobar S. · Diulas 1 hari lalu

Komal P. · Diulas 1 hari lalu

RAMESH A. · Diulas 1 hari lalu

Rohith B. · Diulas 1 hari lalu

Preet J. · Diulas 1 hari lalu

Kaviyarasu P. · Diulas 1 hari lalu

Eishaan K. · Diulas 1 hari lalu

Saikrishna V. · Diulas 1 hari lalu

Kanika B. · Diulas 1 hari lalu

ᎪຮᏂυtoຮᏂ B. · Diulas 1 hari lalu

Monisha K. · Diulas 1 hari lalu

I'm very satisfied by doing this lab

Avadhut G. · Diulas 1 hari lalu

the agent.json no such file or directory is found

Mithra G. · Diulas 1 hari lalu

Priya .. · Diulas 1 hari lalu

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. · Diulas 1 hari lalu

time is so less

Dhwnit S. · Diulas 1 hari lalu

nice

Parminder K. · Diulas 1 hari lalu

Mahesh p. · Diulas 1 hari lalu