Implement Controlled Fault Injection for Localization Replay

Abierto
#763 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
Área
testing

Línea de trabajo

No files or tests are named in the payload. Start by locating Awkernel's localization replay pipeline and its scenario/configuration entry points, then identify where input streams, timestamps, message delivery, logging, and competing tasks are handled. Done means reproducible fault scenarios with recorded configuration/events, tests checking injected events against their specification, and documented seeds/reproduction commands.

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

Descripción

Implement reproducible injection of input delays, timestamp offsets, dropped messages, and computational overload into localization replay experiments on Awkernel. Exercise the integrated pipeline under controlled abnormal conditions without modifying the original datasets.

Scope:

  • Inject configurable delivery delays and jitter into selected input streams
  • Apply timestamp offsets independently of delivery timing
  • Drop individual messages or configurable bursts using deterministic rules or seeded randomness
  • Introduce controlled computational load through configurable competing tasks
  • Support isolated faults and explicitly defined combinations
  • Record the injection configuration and actual events observed during each run

Acceptance criteria:

  • Each scenario specifies the target stream or task, injection point, start time, duration, and magnitude.
  • Delivery-delay injection preserves measurement timestamps unless timestamp modification is explicitly enabled.
  • Timestamp-offset injection changes only the configured timestamp fields and documents how per-point times are affected.
  • Drop patterns are reproducible, and injected losses are distinguishable from pipeline overflow or processing failures.
  • Computational-load scenarios specify workload, CPU affinity, priority, and activation pattern, with actual interference measured.
  • Replay continues to offer inputs at the configured rate rather than slowing down to match processing completion.
  • Fault-free control runs use the same datasets and baseline configuration.
  • Tests verify that injected events match their specification; deviations caused by scheduling are recorded.
  • Logs retain original and modified timing information, message identifiers, and injection decisions.
  • Scenarios, seeds, configurations, and reproduction commands are documented.

Out of scope:

Defining recovery policies, modifying localization algorithms, physical sensor faults, and vehicle-level safety validation.

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.