M4: Reusable Components, Security Hardening, and Performance Optimization

Ouverte
#766 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Refactorisation
Clarté
Plutôt claire
Activité
Active
Stack technique
linux, rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
282
Forks
12
Merge moyen
2 j 9 h
PR mergées (30 j)
28

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de tier4/awkernel

Toutes les issues de tier4/awkernel

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.