0xMiden / 0xMiden/note-transport-service
Server errors exit with code 0 — restart-on-failure never triggers
Aberta
bug
production-readiness
- Linguagem predominante
- Rust
- Estrelas
- 3
- Forks
- 10
- Merge médio
- 2h 23min
- PRs com merge (30d)
- 4
Descrição
Severity: high (bug).
### Summary
`entrypoint()` swallows the server error: `if let Err(e) = self.grpc.serve().await { error!("Server error: {e}"); }` (`crates/node/src/node/mod.rs:59-61`), and `main` then returns `Ok(())` (`bin/node/src/main.rs:83`).
### Impact
A bind failure, transport error, or any fatal server error produces a clean `exit(0)`. Docker `restart: on-failure` and systemd `Restart=on-failure` treat this as success and leave the service down.
### Recommendation
Propagate the error from `entrypoint()` to `main` so the process exits non-zero on fatal error.
---
Part of #114.
Guia de contribuição
Avaliação
Esta issue ainda não foi avaliada.