Function loadTrafficProtocols

web/scripts/ragnar_modern.js:16035–16089

()

        setTimeout(() => {
            verifyServiceRestart(data.to_commit || '');
        }, 5000);

    } catch (error) {
        console.error('Update error:', error);
        if (isLikelyNetworkError(error)) {
            // The service may have restarted before the response reached us -
            // verify the outcome instead of declaring failure.
            addConsoleMessage('Connection dropped while updating - verifying whether the update completed...', 'info');
            updateElement('update-info', 'Connection dropped. Verifying update...');
            setButtonState(true, 'Verifying...');
            setTimeout(() => {
                verifyServiceRestart('');
            }, 5000);
            return;
        }
        const payload = error.payload || { error: error.message };
        if (payload.code === 'busy') {
            // Two tabs, two clicks. The other one is doing the work - follow it
            // rather than reporting a failure that did not happen.
            addConsoleMessage('An update is already running on this box - watching it instead.', 'info');
            setButtonState(true, 'Updating...');
            verifyServiceRestart('');
            return;
        }
        const message = reportUpdateProblem('Update failed', payload);
        setButtonState(false, idleLabel);
        updateElement('update-info', payload.hint || `Update failed: ${message}`);
    }
}

// Watch the box through the restart. Ragnar hands the tail of an update
// (dependency installs, provisioning) to a transient systemd unit that restarts
// the service when it is done, so "the API answers" is not the same as "the
// update finished" - the commit the box reports has to change too.
async function verifyServiceRestart(expectedCommit) {
    let attempts = 0;
    // 5 minutes of silence is the giving-up point, but post-update work that is
    // demonstrably still running extends it: a dependency install or an
    // apt-get update on a Pi routinely outlasts five minutes, and reporting
    // "could not confirm the update" over a step that is plainly making
    // progress is a false alarm about a box that is perfectly fine.
    let maxAttempts = 60;
    const hardCeiling = 360;         // 30 minutes, even with progress
    let sawRestart = false;
    let lastStep = '';
    // The service reports when this process started. A change in that value is
    // proof the restart happened, which is more reliable than hoping to catch
    // the box unreachable between two five-second polls.
    let startedAt = null;

    addConsoleMessage('Verifying the update landed and the service is back...', 'info');
    updateElement('update-info', 'Verifying update...');

    const finish = (message, level, info) => {
        addConsoleMessage(message, level);
        updateElement('update-info', info);
        const updateBtn = document.getElementById('update-btn');