Skip to content

v0.72.0

Choose a tag to compare

@hhff hhff released this 20 Nov 10:38
5ce813f

What

  • The box's gateway serves the hub's memory readings at /memory.json, to signed-in people only. It forwards only checked since and after values, sends no browser headers to the hub, and gives a 502 when the hub is down, slow (15 s), or answers more than 2 MiB (kit-599 #448).
  • dispose refuses a findings row whose cell count isn't the header's, instead of writing into the wrong cell. Escaped \| counts as text. check-ticket's warning about such rows now says to fix the row's shape first (kit-338 #449).
  • No GET request to the dashboard changes anything. The Settings page's Check now, which fetches from git, is now POST /api/fleet-check with the owner actions' same-origin checks; GET /api/fleet never fetches, whatever its query (kit-251 #450).

Why

  • Approved goal: box memory monitoring (kit-599).
  • Approved goal: org access, where a viewer through the gateway must not change anything (kit-251).
  • Upkeep: a review record could lose its Fix text when a finding held an unescaped | (kit-338).

Migration

This is a minor, and the box redeploys, because the gateway changed.

After adopting:

  • Nothing to change for existing sessions; /memory.json is new.
  • Reload open dashboard tabs and restart the dashboard after upgrading: an old tab's Check now gets an unfetched read, and a new page against an old dashboard gets a 404, until both are current.
  • A findings row with an unescaped | must have its pipes escaped (\|) before dispose will fill it. About 80 such rows exist in closed tickets; they need no action unless disposed again.