Se connecter à des agents distants avec ADK et le SDK Agent2Agent (A2A) avis

Kusum A. · Examiné il y a environ un mois

there is issue face in task 2 and 4 no one output get from agent

Parth N. · Examiné il y a environ un mois

good

Varsha Priya J. · Examiné il y a environ un mois

**Lab Review: Connect to Remote Agents with ADK and A2A SDK** This lab covers an interesting and important concept—enabling communication between AI agents using A2A and ADK. The overall structure and learning objectives are clear, and the hands-on approach is valuable for understanding how multi-agent systems work in practice. However, the lab has significant technical issues that impact the learning experience. The primary problem is that the agent often fails to respond during testing, even when all steps are followed correctly. This appears to be due to backend configuration or Vertex AI access issues, rather than user error. Unfortunately, these failures happen silently, with no meaningful error messages, making it difficult to debug. Additionally, the lab does not clearly explain critical setup steps such as configuring the `.env` file with valid model IDs. The provided placeholders can easily mislead users and cause the agent to fail without explanation. Suggestions for improvement: * Ensure Vertex AI and model access are fully functional in all lab instances * Add proper error handling and clearer logs when model calls fail * Provide correct default model IDs instead of placeholders * Include a troubleshooting section for common issues Overall, the concept is strong, but the execution needs improvement. Currently, the lab can lead to wasted time and credits due to issues outside the learner’s control.

Khush P. · Examiné il y a environ un mois

Amrita Deviayu T. · Examiné il y a environ un mois

Jayandhan S. · Examiné il y a environ un mois

things are not working properly even when followed all instructions properly

Siddh S. · Examiné il y a environ un mois

Kavish N. · Examiné il y a environ un mois

i am getting only 404 error

Siddhant G. · Examiné il y a environ un mois

Cloud shell editor failed to launch adk web with 403 forbidden error. I tried Incrementing the authuser=1 & 2 but didn't work! My credits got wasted.

Mohith L. · Examiné il y a environ un mois

steps are not clear

Vedhakshari Kumari G. · Examiné il y a environ un mois

Arnab C. · Examiné il y a environ un mois

Htut K. · Examiné il y a environ un mois

Swayam J. · Examiné il y a environ un mois

Muhammed R. · Examiné il y a environ un mois

the project did not run in the editor

Jai D. · Examiné il y a environ un mois

Eshwar R. · Examiné il y a environ un mois

Roopa S. · Examiné il y a environ un mois

Priyanshu N. · Examiné il y a environ un mois

There was an issue in the Task 2 , where the server was giving 403 Forbidden irrespective of the authuser value. There was no solution provided. Finally after removing the current session and explicitly origins Fix the issue, But it took alot of time as it was mentioned not to use any commands not mentioned in the course. Please update this solution in the course for better experience. rm -rf /home/student_01_ce4dfaf8af6c/adk_and_a2a/.adk/session.db adk web --allow_origins="*"

Richa C. · Examiné il y a environ un mois

Alexandru C. · Examiné il y a environ un mois

wiku b. · Examiné il y a environ un mois

I faced an issue in Task 2 and Task 4 where the session ID did not appear after launching the ADK Web UI. The interface loaded, but no session was created and the agent did not respond. The console repeatedly showed "403 Forbidden" errors when trying to create sessions. I tried restarting the server, creating new sessions, and adjusting the authuser parameter, but the issue persisted. This made it difficult to complete the required steps involving agent interaction and remote calling.

Krupal S. · Examiné il y a environ un mois

very poor not able to start the session

Pyush B. · Examiné il y a environ un mois

403 issue everytime.

HariPrasad K. · Examiné il y a environ un mois