Define and Implement Input Freshness and Overload Policies

Ouverte
#764 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
18/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust

Piste de recherche

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.

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

Description

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.

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.