YADM repo for system level files
- Go 91%
- Shell 2.9%
- JavaScript 2.4%
- CSS 1.8%
- Dockerfile 1.5%
- Other 0.4%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
BA1001
f9d068997f
The found path reported 100 and called location.replace in the same synchronous block, so the browser painted neither the 100 nor the 80ms .progress-fill transition it starts. The bar was seen frozen wherever it last stood -- 63% of the way, at the mean, so typically 40-60% -- and the destination simply appeared. Both exits now wait: SETTLE_MS normally, PAINT_MS under prefers-reduced-motion, which deletes the transition and leaves only the frame that is still owed. 200ms clears the worst case at 60Hz of a frame to start the transition, 80ms to animate, and a frame to present. noRedirect=1 settles too. It does not navigate, but it does hide the bar, so without the wait the bar vanished while still showing its last pre-100 value and the completed state was never seen at all. The matchMedia call is guarded. It is the page's only cosmetic call and the only new way the completion path can throw; unguarded, a host without it would strand an already-solved proof here permanently, re-solving on every reload, since each reload draws a fresh nonce and never trips the sessionStorage guard. Verified with the offline harness, which now pins the departure to a strictly later slice than the 100 and requires the wait to cover the transition duration read out of style.css rather than a copied constant. Re-introducing the defect, a zero wait, a too-short wait, a reduced-motion branch that ignores the setting, and the missing guard each fail it. The new assertions fail against the previously deployed file. |
||
| etc | ||
| opt | ||
| root | ||
| usr/local/jilits | ||
| README.md | ||
JILITS System Files Repository
This repository contains system configuration files managed by yadm for simplified deployment and bootstrap of system files.
System Initialization Instructions
To set up the repository on a fresh system, use the provided one-liner below to download and execute the initialization script.The script initializes, clones, and configures yadm for system-wide usage.
curl -fsSL https://git.jilits.se/JILITS/sysfiles/raw/branch/main/usr/local/jilits/sysyadm-init.sh -o /tmp/sysyadm-init.sh && bash /tmp/sysyadm-init.sh
Initialization Prerequisites
- System Requirements: A Debian-based system (Ubuntu, Debian, etc.).
- Git Access: Ensure you can add the SSH key to the Git server (
git.jilits.se).
Generated SSH Key
The script generates an SSH key for the root user if it does not already exist. The public key will be printed during execution. Make sure to add the SSH key to the Git server to allow cloning.
Troubleshooting
If the script fails:
- Ensure you are not running the script as the root user.
- Verify internet connectivity and access to the Git repository.
- Check that you have permissions to install packages using
sudo.