naturallaw777
64624002bb
The full-system updater runs as a detached systemd service and can finish successfully even when the browser loses its status connection. In that case the update log and status file correctly report REBOOT_REQUIRED, but the Hub modal can remain on "Updating..." with its controls disabled. There were four independent ways for the frontend to get stuck: * update status fetches had no deadline, so a request that stayed pending never rejected and never advanced the existing failure counter; * setInterval started async polls without waiting for the previous poll, allowing slow requests to overlap and responses to arrive out of order; * each log chunk used textContent +=, replacing the complete and growing Nix build log every two seconds, which could stall browser rendering and was especially visible over RDP; and * page reload, tab resume, and RDP reconnect did not reattach the modal to the update status persisted by the backend. This produced a dangerous UX mismatch: the machine had a fully staged NixOS generation and was ready to reboot, while the Hub continued telling the user that the update was still running. Bound status requests with AbortController, prevent overlapping polls, and replace the endless spinner after sustained failures with an explicit "Update status unavailable" state and Retry Status action. Reconcile state immediately on focus, visibility, online, page startup, and before starting a new update. Use no-store requests and render verbose logs incrementally with a bounded visible tail while retaining the complete report in memory. Apply the same timeout and single-flight protection to rebuild polling. Record the exact generation produced by `nixos-rebuild boot`. The Hub now keeps REBOOT_REQUIRED visible until that generation matches /run/current-system, then clears the marker after reboot. For an update started by an older updater that did not write the marker, recover the staged generation from the final nixos-rebuild log line. The dashboard sidebar also distinguishes update-in-progress and restart-required states. Regression coverage verifies generation marker/log recovery, pre- versus post-reboot detection, request timeout wiring, single-flight polling, connection-loss UX, RDP/tab resume reconciliation, bounded log rendering, page-reload recovery, and JavaScript syntax. Validation: * python3 -m unittest discover -s tests -p 'test_*.py' -v (170 passed) * node --check app/sovran_systemsos_web/static/js/*.js * python3 -m py_compile for changed Python modules * git diff --check A Nix evaluation was not available in the development sandbox; the NixOS module should still be evaluated and built in CI or on a test machine before release.
45 lines
1.6 KiB
JavaScript
45 lines
1.6 KiB
JavaScript
/* Sovran_SystemsOS Hub — Vanilla JS Frontend
|
|
v7 — Status-only dashboard + Tech Support + Feature Manager */
|
|
"use strict";
|
|
|
|
const POLL_INTERVAL_SERVICES = 5000;
|
|
const POLL_INTERVAL_UPDATES = 1800000;
|
|
const UPDATE_POLL_INTERVAL = 2000;
|
|
// A pending fetch never rejects by itself. Bound every status request so a
|
|
// wedged browser connection cannot leave the modal spinning forever.
|
|
const STATUS_POLL_FETCH_TIMEOUT = 15000;
|
|
// Eight timed-out requests plus the poll interval is a little over two minutes.
|
|
// A brief Hub restart or a heavily loaded Nix build remains well inside this.
|
|
const STATUS_POLL_MAX_FAILURES = 8;
|
|
// Keep verbose Nix output from making textContent updates quadratic and
|
|
// freezing the Hub renderer (especially noticeable over RDP).
|
|
const UPDATE_VISIBLE_LOG_MAX_CHARS = 250000;
|
|
const UPDATE_VISIBLE_LOG_TRIM_CHARS = 200000;
|
|
const REBOOT_CHECK_INTERVAL = 5000;
|
|
const REBOOT_FETCH_TIMEOUT = 12000;
|
|
const REBOOT_REQUEST_TIMEOUT = 4000;
|
|
const REBOOT_INITIAL_DELAY = 25000;
|
|
const SUPPORT_TIMER_INTERVAL = 1000;
|
|
|
|
const CATEGORY_ORDER = [
|
|
"infrastructure",
|
|
"bitcoin-base",
|
|
"bitcoin-apps",
|
|
"communication",
|
|
"apps",
|
|
"nostr",
|
|
];
|
|
|
|
const FEATURE_SUBCATEGORY_LABELS = {
|
|
"infrastructure": "🔧 Infrastructure",
|
|
"bitcoin": "₿ Bitcoin",
|
|
"communication": "💬 Communication",
|
|
"nostr": "📡 Nostr",
|
|
};
|
|
|
|
const FEATURE_SUBCATEGORY_ORDER = ["infrastructure", "bitcoin", "communication", "nostr"];
|
|
|
|
const STATUS_LOADING_STATES = new Set([
|
|
"reloading", "activating", "deactivating", "maintenance",
|
|
]);
|