M4: Reusable Components, Security Hardening, and Performance Optimization

Abierto
#766 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
15/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux, rust

Línea de trabajo

This is a multi-part milestone with no specific files named, so start by reading the existing realtime_core libraries and the M1–M3 evaluation tests and datasets the issue refers to. Agree on one small behavior-preserving extraction with maintainers before writing code. Done means the extracted core builds without Awkernel-specific dependencies and the relevant M1–M3 comparison tests still pass within their tolerances.

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

Descripción

Refactor the sensing and localization components into reusable, platform-independent libraries that can run on Awkernel and other environments. Improve security, robustness, and performance while preserving validated behavior and reusing the evaluation infrastructure established in M1–M3.

Scope:

  • Build on the existing realtime_core libraries and consolidate reusable functionality without duplicating implementations
  • Separate algorithmic cores from platform-specific scheduling, communication, timing, logging, and synchronization adapters
  • Define APIs, ownership rules, initialization and reset behavior, and memory and resource contracts
  • Demonstrate reuse on Awkernel and a Linux-hosted test application
  • Harden input validation, resource limits, and unsafe or FFI boundaries
  • Add fuzz testing, property-based testing, and regression cases for malformed and extreme inputs
  • Optimize measured bottlenecks such as copying, allocation, data layout, and synchronization
  • Establish shared regression tests and CI coverage for supported environments

Completion criteria:

  • Shared cores can be built and used without Awkernel-specific dependencies, with documented platform requirements and feature configurations.
  • The same core implementations are exercised through Awkernel and Linux adapters using shared test datasets.
  • Behavior-preserving extraction passes the applicable M1–M3 comparison and regression tests within predefined tolerances.
  • Input-validation rules, resource bounds, and unsafe or FFI assumptions are documented and tested against a defined threat model.
  • Security findings are resolved or explicitly documented with their impact and mitigation.
  • Performance changes are evaluated against a fixed baseline, reporting accuracy, tail latency, maximum observed execution time, allocation and copy counts, and peak memory usage where applicable.
  • Optimization targets and permitted regressions are defined before evaluation; trade-offs are explicitly reported.
  • APIs, integration examples, build configurations, and reproduction steps are documented.

Implementation approach:

Separate behavior-preserving extraction from optimization and intentional behavior changes. Architecture work may begin before M3 is complete, but final acceptance must use the relevant M1–M3 validation assets. Essential input safety and known vulnerability fixes must not be deferred until M4.

Out of scope:

New perception or planning functionality, mandatory ROS 2 runtime dependencies in shared cores, kernel-level fault isolation, formal security certification, and formal worst-case execution-time guarantees.

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.