Skip to content

Firmware library: checking, not unavailable, until the catalogue answers - #777

Merged
A13xB0 merged 2 commits into
mainfrom
fix-772-firmware-checking
Oct 24, 2026
Merged

A13xB0 merged 2 commits into
mainfrom
fix-772-firmware-checking

Conversation

@A13xB0

@A13xB0 A13xB0 commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator

Fixes #772.

A row for a build that isn't on disk was marked unavailable whenever it wasn't in the published list, and that list is empty until the catalogue fetch returns, or permanently if the fetch fails. So on a fresh install the library opened by calling the fixture's builds "not published for this machine", right where Setup sends new users.

Rows not on disk now have three states:

  • checking: the fetch hasn't answered yet.
  • catalogue unreachable: the fetch failed. The action is retry, which rescans.
  • unavailable: the catalogue answered and the build isn't in it.

firmware.library rows carry checking and catalogue_down. The Actions column is widened from 70 to 96 dp, so "unavailable" no longer wraps.

The native builds and the board images come from two catalogues, and each one's failure is tracked separately. A board row isn't called unavailable when only the native catalogue was unreachable, or the other way round. The Go and Python clients' Build have the two new fields.

@A13xB0
A13xB0 force-pushed the fix-772-firmware-checking branch from 8232737 to 3d86888 Compare October 24, 2026 19:36
…not unavailable

On a fresh install the library called every pinned build unavailable
until the catalogue fetch came back, which is exactly when Setup sends a
new user there. Rows now say checking while the fetch runs, and say the
catalogue could not be reached (with a retry) when it fails, rather than
claiming the build is not published. The Actions column is wide enough
for its labels.

Fixes #772
A row for a board image said "unavailable" when the board catalogue could
not be reached, because only the native catalogue's failure was kept. Each
half now has its own, and the library rows' new fields are documented and
in the Go and Python clients.
@A13xB0
A13xB0 force-pushed the fix-772-firmware-checking branch from 3d86888 to be1da42 Compare October 24, 2026 19:47
@A13xB0
A13xB0 merged commit afce880 into main Oct 24, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Firmware library says "not published for this machine" before the catalogue has loaded

1 participant