Degrade gracefully when Iroh modules fail
This commit is contained in:
parent
ed007a0632
commit
7d67da9dfe
4 changed files with 193 additions and 55 deletions
|
|
@ -26,6 +26,17 @@ For deployment-readiness work that cuts across feature areas, see
|
|||
- `[x]` Stale, unreachable socket paths are recovered automatically.
|
||||
- `[x]` Tests cover stale recovery and live second-daemon rejection.
|
||||
|
||||
- `[x]` Keep local control available when Iroh-native startup degrades.
|
||||
Acceptance criteria:
|
||||
- `[x]` Endpoint startup and native blob/docs/gossip initialization failures
|
||||
do not prevent the local control daemon from serving.
|
||||
- `[x]` Partial native runtime handles are released and a partially started
|
||||
endpoint is closed.
|
||||
- `[x]` Status reports each native backend as unavailable with the runtime
|
||||
failure note instead of claiming a compiled backend is healthy.
|
||||
- `[x]` Tests inject a post-endpoint native-store failure and verify clean
|
||||
degradation where UDP endpoint binding is available.
|
||||
|
||||
- `[x]` Make startup modes and the daemon lifecycle discoverable.
|
||||
Acceptance criteria:
|
||||
- `[x]` Base and nested CLI help explain every command family instead of
|
||||
|
|
|
|||
Loading…
Reference in a new issue