bug: an unknown --a2a-version is not a usage error
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
Research direction
The flag value is accepted without validation, so unknown versions fall through to clientFactoryOpts, where no transports get registered. Start by finding where --a2a-version is parsed and where the 'no compatible transports found' error is produced. Done means an unsupported value fails early as a usage error that names the flag and lists the accepted values. Pull request #157 is already open against this issue, so check it before starting.
Written by the indexing model from the issue text.
Description
What happened?
--a2a-version only accepts 1.0 or 0.3. Any other value registers no transports in clientFactoryOpts, so the command fails with no compatible transports found, exit 1 as A2ACLI_ERR_INTERNAL. If the card can't be reached it exits 3 with a connectivity hint instead. Nothing says the flag value is the problem.
Steps to reproduce
a2a server --echo --port 18431a2a send -a http://127.0.0.1:18431 --a2a-version 1 hiexits 1 with:
Error: failed to create a client: no compatible transports found: available transports - [HTTP+JSON_1.0]
a2a send -a http://127.0.0.1:1 --a2a-version 1 hiexits 3 withfailed to resolve agent card.
CLI version
main @ 5c95123
Operating system & environment
macOS (Darwin 25.6.0), arm64
- Dominant language
- Go
- Stars
- 181
- Forks
- 28
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from a2aproject/a2a-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
a2aproject/a2a-cli#159 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
a2aproject/a2a-cli#158 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
a2aproject/a2a-cli#15 · 2 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
bug: [flagparse] loopback references with paths default to HTTPSPossibly taken @ktsoator claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
a2aproject/a2a-cli#162 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
a2aproject/a2a-cli#160 ·
Maintainers usually reply within 2 days
All issues in a2aproject/a2a-cli
Similar issues
-
ssa: wait errors drop the kstatus message, so health check failures don't say whyPossibly taken @schdief claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Pin and verify Security Insights schema in lintinsights targetPossibly taken @imshubham22apr-gif claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gemaraproj/gemara#618 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
a2aproject/a2a-go#597 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
scopes: GetAllowedTopics, GetProtectedTopics, and GetScopedTopics include empty topic names and do not trim whitespace charactersPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day