[Bug] B22: peer cloud download 'Operation failed' + audio error (.228→.198) #30

Closed
opened 2026-06-15 20:53:44 +00:00 by lfg2025 · 1 comment
Owner

Downloading a peer cloud file → 'Operation failed. Check server logs.'; playing peer audio → 'Could not play audio. File Browser may not be running' (misleading — old base64 path B3 replaces). Needs live repro watching .198 logs. Pairs with B3. (tracker: tests/production-quality/TRACKER.md on vps2 main)

Downloading a peer cloud file → 'Operation failed. Check server logs.'; playing peer audio → 'Could not play audio. File Browser may not be running' (misleading — old base64 path B3 replaces). Needs live repro watching .198 logs. Pairs with B3. (tracker: tests/production-quality/TRACKER.md on vps2 main)
Author
Owner

Fixed in commit e456c970 (audio error previously fixed in c481afc7). The download path now (1) makes the FIPS client honor the caller's timeout instead of a hard-coded 20s cap (the mesh->Tor fallback already exists in send_get), (2) streams the peer body instead of buffering the whole file, and (3) surfaces the real error (peer offline on mesh and Tor) instead of the generic 'Operation failed'. Pending live deploy verification.

Fixed in commit e456c970 (audio error previously fixed in c481afc7). The download path now (1) makes the FIPS client honor the caller's timeout instead of a hard-coded 20s cap (the mesh->Tor fallback already exists in send_get), (2) streams the peer body instead of buffering the whole file, and (3) surfaces the real error (peer offline on mesh and Tor) instead of the generic 'Operation failed'. Pending live deploy verification.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lfg2025/archy#30
No description provided.