Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Proposal: durable cA2A task submissions and safe retries

Aperta
  • Qualcosa non va?
#301 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend-api-design, distributed-systems, security

Direzione di ricerca

Start by reading the current authenticated-response profile and its stated limits on deduplication and restart recovery, then review the upstream A2A safe-retries discussion at a2aproject/A2A#1942. The proposal calls for a threat model, contract document, persistent ledger, and official A2A SDK integration test; first agree the profile scope and holder-proof binding with maintainers. Done means an approved design and tests covering duplicate requests, conflicting content, and crash uncertainty.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Problem statement

I'm a first-time contributor interested in cA2A's A2A integration. If a caller sends a delegated task but loses the response, it may not know whether the callee executed it. Retrying can invoke the handler again. The current authenticated-response profile explicitly leaves request execution deduplication and restart recovery out of scope.

Proposed solution

I'd like to explore an opt-in durable-task profile that binds a stable intent ID and digest to the holder proof, then atomically stores the authorized intent and A2A Task ID before dispatch. A repeated valid request with the same principal and intent would return the existing Task ID without another handler invocation; the same ID with different content would be refused. A crash during execution would remain explicitly uncertain until reconciled, rather than being retried automatically.

I would start with a contract and threat-model document, then a small persistent ledger and an official A2A SDK integration test. I'm asking for scope and design feedback before coding. I'm also requesting a first-contributor vouch for @adityardesai if this is an appropriate area to work on. I used Codex to help draft this proposal, and will review and understand any change I submit.

Alternatives considered

  • Reusing only record_id or the current response session: neither is a durable idempotency contract. The response session is intentionally one-use.
  • Retrying every timed-out request: this can duplicate side effects.
  • Defining a general A2A idempotency mechanism here: upstream A2A is discussing safe retries in a2aproject/A2A#1942. This proposal should align with that work.

Security/TEE impact

This changes the authorization boundary: the stable intent must be bound to the verified holder and all inputs the protected handler uses. The ledger must reserve atomically across workers and fail closed when unavailable. This proposal makes no new TEE or exactly-once external-effect claim.

Spec alignment

No trace-spec change is proposed in the first phase. A versioned cA2A extension/profile and holder-proof binding would need maintainer review. The official A2A Task and message-send semantics should remain intact.

Lingua principale
Python
Stelle
9
Fork
14
Merge medio
1g 8h
PR unite (30g)
36

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di agentrust-io/ca2a

Tutte le issue di agentrust-io/ca2a

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.