d1e75ddded
Move issues (01–29) and PRD from .scratch/distributed-inference-network/ into docs/issues/ and docs/. Update ralph_progress.py DEFAULT_PRD path and rewrite docs/agents/issue-tracker.md to reflect the new layout. The distributed_inference_network.egg-info/docs/ mirror is a build artifact already covered by *.egg-info/ in .gitignore — not committed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
20 lines
815 B
Markdown
20 lines
815 B
Markdown
# US-021 — `--route-timeout` CLI flag for node tracker route lookup
|
|
|
|
Status: done
|
|
Priority: Medium
|
|
Stage: Implemented
|
|
|
|
## Context
|
|
|
|
The node's slow-path tracker route lookup (`/v1/route`) used a hard-coded 30-second HTTP timeout.
|
|
On high-latency links (relay, satellite, 5G) or when the tracker is under load, legitimate route
|
|
lookups were failing prematurely. The timeout is deployment-specific and should be tunable.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [ ] `meshnet-node start` accepts `--route-timeout <seconds>` (float, default 30.0)
|
|
- [ ] Value is passed through to `TorchNodeServer` and used in the `/v1/route` HTTP call
|
|
- [ ] `TorchNodeServer` exposes `route_timeout` as a readable property
|
|
- [ ] Test: setting `--route-timeout 45` is reflected as `45.0` on the running server object
|
|
- [ ] `python -m pytest` passes
|