Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Proposal: durable cA2A task submissions and safe retries

Abierto
  • ¿Algo no está bien?
#301 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend-api-design, distributed-systems, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
9
Forks
14
Merge medio
1 d 8 h
PR fusionados (30 d)
36

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de agentrust-io/ca2a

Todos los issues de agentrust-io/ca2a

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.