Define and Implement Input Freshness and Overload Policies

Abierto
#764 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

Start by reading the Awkernel localization pipeline modules that ingest input streams, hold buffers, and publish status events; the issue names no files, so map each input stream and its current timeout, buffer, and deadline handling first. Then draft the policy matrix from the acceptance criteria before touching code, and use it to drive implementation and fault-injection tests. Done means the matrix is documented, bounded/configurable behavior is implemented, and tests cover stale inputs, missing messages, overflow, overruns, and late results.

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

Descripción

Define and implement explicit policies for stale or missing inputs, bounded buffers, and processing overruns in the Awkernel localization pipeline. Ensure that abnormal conditions produce observable and predictable behavior rather than unbounded backlog or silently invalid estimates.

Scope:

  • Define freshness limits and missing-input timeouts for each input stream
  • Specify buffer capacities and overflow behavior, such as dropping oldest or newest messages
  • Define component-specific behavior when required data is unavailable, including bounded waiting, skipping updates, or explicitly flagged fallback
  • Define handling of deadline overruns, overlapping activations, and late results
  • Specify recovery conditions and estimator-reset behavior where necessary
  • Report policy decisions through structured status events and counters

Acceptance criteria:

  • A policy matrix documents each condition, detection rule, threshold, action, output-validity status, and recovery condition.
  • Waiting periods and buffer capacities are bounded and configurable.
  • Component-specific requirements are respected; motion history is not discarded while still required for an admitted scan without an explicit failure outcome.
  • Stale or missing data is not silently reused as a fresh measurement, and prediction-only outputs are distinguishable from measurement-updated outputs.
  • Deadline overruns do not create uncontrolled overlapping executions or unlimited catch-up work.
  • Late or cancelled computations cannot overwrite newer state or access released buffers; cancellation is used only where supported safely.
  • Fault-injection tests verify the expected behavior for stale inputs, missing messages, buffer overflow, processing overruns, and recovery.
  • Logs distinguish input rejection, queue overflow, skipped updates, deadline misses, and discarded late results.
  • Any deviations from the selected Autoware reference behavior are documented.

Out of scope:

Fault-injection infrastructure, new scheduling algorithms, vehicle-level emergency-stop behavior, and formal safety certification.

Lenguaje dominante
Rust
Estrellas
282
Forks
12
Merge medio
2 d 9 h
PR fusionados (30 d)
28

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 tier4/awkernel

Todos los issues de tier4/awkernel

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.