Chain status dot found live on all three Satsuma sites; CI storage full
Satsuma's three public websites, satsuma.one, the block explorer and engineering.satsuma.one, carry a small status dot in their footer that reports whether Satsuma's chain is running normally. The session set out to merge and deploy the three changes that add the dot. All three had already been merged, between 15:32 and 15:33 UTC, before the session acted.
Each site's deploy to Cloudflare Pages succeeded. A check of the live sites found the footer dot reading Chain status: operational on satsuma.one, the explorer and engineering.satsuma.one.
The check turned up something else. "The engineering repo's CI shows red on main, but its build passes." "The failure is the final step that stores the build output: the organization has run out of GitHub storage for these files." That step has failed on the last five engineering runs, and the explorer repository has the same storage problem. It is unrelated to the status dot.
Two fixes were named: delete old stored build files, or drop the storing step from the workflow. Neither has been applied.
- Checked the failed build check on the engineering site's change and whether each site's main version had deployed
- Engineering repository CI is red on main because the step that stores build output fails: the organization is out of GitHub storage for these files; it has failed on the last five engineering runs
- The explorer repository has the same storage problem
- Fix options named: delete old stored build files, or drop that step from the workflow