Define and Implement Input Freshness and Overload Policies

Aberta
#764 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
18/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
282
Forks
12
Merge médio
2d 9h
PRs com merge (30d)
28

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de tier4/awkernel

Todas as issues de tier4/awkernel

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.