You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(a2a): migrate off EventQueueLegacy in SellerA2AClient and test helpers #699
The class name advertises its own deprecation. The a2a package presumably exposes a non-legacy queue elsewhere, or will.
What to do
Confirm what the non-legacy replacement is in the current a2a-sdk version pinned in pyproject.toml. If a successor exists, migrate the harness and any other internal call sites.
If no successor exists yet, open a tracking issue upstream and add a comment in harness.py pointing at it so this isn't lost.
Same check applies to any other *Legacy symbols in the same import surface.
Why this matters
Test harnesses are the slowest-moving surface area an adopter sees. If the a2a-sdk ever drops EventQueueLegacy entirely, the SDK's primary A2A test client breaks for everyone simultaneously.
Acceptance
Audit complete: which a2a.server.events.*Legacy symbols are in use, what their successors are, and migration done OR upstream tracking issue linked
SellerA2AClient on the non-legacy queue when one exists
Activity
bokelley commentedon May 14, 2026
Manual triage.
Verdict: ready-to-draft. Small mechanical chore (~50 LoC + audit).
Action:
grep -rn "Legacy" $(python -c "import a2a; print(a2a.__path__[0])")— find every*Legacysymbol in a2a-sdkEventQueueexists at the pinned a2a-sdk version, migrateSellerA2AClient.invoke()+ any other call siteharness.pySingle-PR scope. No blockers.
chore(a2a): document EventQueueLegacy as the only typeable option (#699…