mirror of
https://github.com/kuhyx/screen-locker.git
synced 2026-11-14 11:10:58 +01:00
Krzysztof kuhy Rudnicki
8f911585c1
The only status surface was a GTK tray icon, commented out of ~/.config/i3 on 2026-08-21. So when the weekly count went wrong, nothing on the machine said so for two weeks -- the same silence that let a deleted timer job stop enforcement for thirteen days in August. Three read-only endpoints, and a React 19 UI over them: /api/status the decision, the week, and whether today has a workout /api/decisions the recorded trail, newest first /api/health timers armed, disarm marker, log and trail freshness The Why view is the one that matters: it renders the run of "weekly_minimum_met 5/5" ticks that hid this week's bug, without anyone having to reach for journalctl. /api/status also carries gaming.workout_today, which is the fact steam-backlog-enforcer will cut the daily budget on. Deliberately just the fact -- the enforcer owns the hour values, so the two repos cannot come to disagree about what a workout day is. It is derived from count_day_credits, the same rule the locker enforces with. _compliance_state_word moves from status_view (tkinter) into _status_projection, and the systemd arming check moves from scripts/check_enforcement_armed.py into screen_locker/_armed_state.py, so the server can answer "is enforcement armed" without a second copy of the logic that would be free to disagree with the gate. web/ mirrors steam-backlog-enforcer/web but tightens it: that config has no "strict" in any tsconfig, extends only tseslint recommended (no type-aware rules at all), and gates neither lint nor typecheck in pre-commit. Here all three run, on strictTypeChecked + stylisticTypeChecked, with noUncheckedIndexedAccess and exactOptionalPropertyTypes. 44 tests, 100% of statements, branches, functions and lines. typescript stays pinned at 6.0.3: 7.0.2 is out, but every published typescript-eslint -- stable, canary and rc-v8 -- declares typescript ">=4.8.4 <6.1.0". The fleet allowlist already carries that entry. The 250-line cap now covers ts/tsx. It was python/shell/dart only, which would have made web/ exempt from the gate the rest of the repo lives under -- the same omission that exempted the whole Flutter app until 2026-08-15. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fcwu78wk17FWMHbbfbyicc
50 lines
1.2 KiB
TypeScript
50 lines
1.2 KiB
TypeScript
import { useEffect, useState } from 'react'
|
|
|
|
export const POLL_MS = 15000
|
|
|
|
interface PollResult<T> {
|
|
readonly data: T | null
|
|
readonly error: string | null
|
|
}
|
|
|
|
/**
|
|
* Poll a fetcher on an interval, keeping the last good value on failure.
|
|
*
|
|
* Deliberately has no `document.hidden` guard. The enforcer's equivalent hook
|
|
* had one and it swallowed the first load, leaving automation-driven tabs stuck
|
|
* on the loading message forever; see steam-backlog-enforcer useBudgetPoll.
|
|
*/
|
|
export function usePoll<T>(
|
|
fetcher: () => Promise<T>,
|
|
intervalMs: number = POLL_MS,
|
|
): PollResult<T> {
|
|
const [data, setData] = useState<T | null>(null)
|
|
const [error, setError] = useState<string | null>(null)
|
|
|
|
useEffect(() => {
|
|
let cancelled = false
|
|
const load = () => {
|
|
fetcher()
|
|
.then((value) => {
|
|
if (!cancelled) {
|
|
setData(value)
|
|
setError(null)
|
|
}
|
|
})
|
|
.catch((e: unknown) => {
|
|
if (!cancelled) {
|
|
setError(e instanceof Error ? e.message : String(e))
|
|
}
|
|
})
|
|
}
|
|
load()
|
|
const handle = setInterval(load, intervalMs)
|
|
return () => {
|
|
cancelled = true
|
|
clearInterval(handle)
|
|
}
|
|
}, [fetcher, intervalMs])
|
|
|
|
return { data, error }
|
|
}
|