Repository navigation
benchpod: usb-network setting, firmware-update reports, CI pin fix - #29
Merged
Merged
Conversation
CI (Merge pull request #27, run 38411480189) failed: firmware 3.9.0 dropped the console upload replies and reworded the locked-LAN and CA/proxy refusals. The CLI still meets the old texts on pods running older firmware, so those entries stay pinned with "removed": "3.9.0" (Check skips them) and the new texts are pinned next to them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Firmware 3.9.0's device-only USB network setting. Reading works over any connection; off goes over the USB link itself (no console), on over the USB console (the link does not exist while it is off); Ethernet, Wi-Fi and the cloud are refused before anything is sent. status shows "network off (turned off on the pod ...)" and the usb fallback says why. The console's "net off (setting)" status is parsed; the new refusal text is pinned. README reference and tests. HW (baea06): show over USB and Ethernet, refused over Ethernet, off over the link, on over the console. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….com After flash-self (the pod before, when it was running, and as it came back) and after install-blobs installed something, the CLI posts the pod's identity public key and name, old/new firmware and gateware, the blobs, the method (dfu, usb_network, usb_console, lan), the CLI version and the time to POST /api/benchpod/firmware-events. Best effort: 5 s timeout, never fails the update, silent when not signed in, one more try on a later run from firmware-reports.jsonl next to the token. Opt out: --no-firmware-report or BENCHPOD_NO_FIRMWARE_REPORT=1 (README section). Tests stub the server. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…g is on Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The usb_network refusal is pinned already, but firmware main gets it only with benchpod-firmware#49; CI checks main. "pending" turns a missing text into no failure until that PR is merged (drop the field then). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…network/5xx/429 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wardviaene
marked this pull request as ready for review
October 13, 2026 14:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #27, for the same release (with benchpod-firmware #49, embeddedci-python #35, embeddedci-server #120).
internal/fwrefusalspinned texts firmware 3.9.0 dropped (console upload replies) or reworded (locked LAN, CA/proxy). Old texts stay pinned with"removed": "3.9.0"(still met on older pods); new texts pinned. A pin can be"pending"on a firmware PR (theusb_networkrefusal, until benchpod-firmware#49 is on main).benchpod usb-network [show|on|off]: the device-only USB network setting. Read anywhere;offover the USB link itself;onover the USB console; refused over Ethernet/Wi-Fi/cloud before sending.statusshows "network off (turned off on the pod ...)", theusbfallback says why.flash-self(pod before/after, blobs it installed) andinstall-blobs, a best-effort report toPOST /api/benchpod/firmware-events(identity public key, name, old/new firmware and gateware, blobs, method, CLI version, time). 5 s timeout, never fails the update, silent when not signed in, one retry on a later run (4xx dropped). Opt out:--no-firmware-report/BENCHPOD_NO_FIRMWARE_REPORT=1. README section.usb-reattachwording;scripts/hw-e2e.sh --flash-args.Tests: go test ./... green (fake server for reports, never the real one). HW (baea06): usb-network on macOS and Windows 11 (off: COM port only, no adapter; on from COM3 brings it back); CLI hw-e2e 19/19 over USB on the #49 build.
🤖 Generated with Claude Code