ddidderr
c00e6eae84
A streamed install sender kept the original frame sink alive outside the producer task. After the producer sent Complete, or an Error for a provider failure, the forwarding loop still had a live mpsc sender in scope and waited forever for another frame. Move the sink into the producer so the channel closes when the producer exits. That lets the QUIC writer close, the request task return, and the outbound TransferGuard drop after successful streamed installs and provider-side failures. The peer-cli harness now keeps the outbound-transfer map it passes into the peer runtime and exposes per-game counts in status. S39 asserts that the source has no active outbound transfer for cnctw after the streamed install finishes, which catches the sender-side lifecycle leak that receiver-only assertions missed. The peer-cli README and scenario table document that status field and expectation. Test Plan: - just fmt - just test - just clippy - git diff --check - git diff --cached --check - python3 crates/lanspread-peer-cli/scripts/run_extended_scenarios.py S39 S40 --build-image - python3 crates/lanspread-peer-cli/scripts/run_extended_scenarios.py S41 S42 S43 S44 S45 S46 S47 Refs: NEXT_STEPS.md streamed install lifecycle hardening
49 lines
1.7 KiB
Markdown
49 lines
1.7 KiB
Markdown
# lanspread-peer-cli
|
|
|
|
Scriptable peer harness for automated LAN-spread tests. The binary starts the
|
|
core peer runtime without the Tauri GUI, reads one JSON command per stdin line,
|
|
and writes JSONL events, results, and errors to stdout.
|
|
|
|
## Running
|
|
|
|
```bash
|
|
just peer-cli-build
|
|
just peer-cli-image
|
|
just peer-cli-run alpha
|
|
```
|
|
|
|
Useful flags:
|
|
|
|
- `--games-dir PATH` stores local archives and installs.
|
|
- `--state-dir PATH` stores the generated peer identity.
|
|
- `--fixture GAME_ID` seeds a tiny archive that the fixture unpacker can install.
|
|
|
|
## Fixture Game Directories
|
|
|
|
`fixtures/fixture-alpha`, `fixtures/fixture-bravo`, and
|
|
`fixtures/fixture-charlie` are ready-to-use game directories for local CLI
|
|
smoke tests. Point `--games-dir` at one of them to start a peer with several
|
|
catalog-backed fake games. Each game includes `version.ini` and a real RAR
|
|
archive renamed to `.eti`; `fixture-alpha` and `fixture-bravo` share `ggoo`,
|
|
while `fixture-bravo` and `fixture-charlie` share `cnc4`.
|
|
|
|
## Commands
|
|
|
|
Every command is a JSON object with `cmd` or `command`; `id` is optional and is
|
|
echoed back on the result or error line.
|
|
|
|
```json
|
|
{"id":"s1","cmd":"status"}
|
|
{"id":"p1","cmd":"wait-peers","count":1,"timeout_ms":5000}
|
|
{"id":"c1","cmd":"connect","addr":"127.0.0.1:34567"}
|
|
{"id":"g1","cmd":"list-games"}
|
|
{"id":"d1","cmd":"download","game_id":"fixture-one","install":true}
|
|
{"id":"i1","cmd":"install","game_id":"fixture-one"}
|
|
{"id":"u1","cmd":"uninstall","game_id":"fixture-one"}
|
|
{"id":"q1","cmd":"shutdown"}
|
|
```
|
|
|
|
The `status` result includes receiver-side `active_operations` and
|
|
sender-side `active_outbound_transfers` counts by game ID, which the scenario
|
|
runner uses to verify transfer lifecycle cleanup.
|