check / check (push) Failing after 1s
The old backend/.golangci.yml declared version "2" but used v1 schema keys, so under v2 it never validated and its thresholds were inert: the linter ran at defaults. Replace it verbatim with the org-standard file, repin the Dockerfile.backend lint stage to golangci-lint v2.12.2, and assert the config's sha256 as the first step of the backend lint target so it cannot silently drift again -- a local hash check, no network. The standard config surfaces findings only in the tests: the repeated IP literals in middleware_test.go become named constants (goconst) and its request switches to NewRequestWithContext (noctx). reportbuf.go's gosec suppression gains a plain justification comment. The rest of the backend, including the fx-based server lifecycle, is already clean. TODO.md updated. Model: opus-4-8
5.9 KiB
5.9 KiB
Workflow
- branch (from
main) - do the work in Next Step
- move Next Step to the top of Completed Steps
- move the top item of Future Steps into Next Step
- commit (
TODO.mdchanges in the same commit as the work) - merge to
mainif the branch is not protected, otherwise open a PR - push
Status
pre-1.0. No git tags. feat/reportbuf-storage is merged; the backend, the CI
workflow, and the backend repo standard files are all on main. Frontend and
backend are both functional. Working toward the 1.0.0 milestone by closing the
remaining repo-compliance issues on the tracker.
Next Step
Confirm the .gitea/workflows/check.yml run is green (main always green
policy). The workflow file is already on main; what is unverified is that its
latest run passes.
Completed Steps
- 2026-09-21: shutdown lifecycle correctness. The process now shuts down through
fx instead of
os.Exit, so every component'sOnStopruns and buffered reports are flushed to disk onSIGTERM— previously a full flush window of telemetry was silently lost on every restart. Thehttp.Serveris now built before its serving goroutine starts, so shutdown can no longer race or nil-deref it; a listen failure exits non-zero viafx.Shutdowner;reportbufOnStopis idempotent; andwriteTimeoutnow exceeds the chi per-request budget so that budget is actually reachable. DeadstartupTime,exitCode, andcancelFuncfields were removed - 2026-09-21: backend HTTP hardening (issue #19): added
ReadHeaderTimeoutandIdleTimeoutto the server, aSecurityHeadersmiddleware (HSTS, tight CSP, frame/sniff/referrer/permissions headers) registered before CORS, and trusted-proxy client IP resolution honouringX-Forwarded-For/X-Real-IPonly from aTRUSTED_PROXIESallowlist (loopback plus RFC1918 by default) - 2026-08-10: adopted the org-standard
backend/.golangci.ymlverbatim and moved the pinned golangci-lint from v2.7.2 to v2.12.2 (thelintstage ofDockerfile.backendnow pins thegolangci/golangci-lint:v2.12.2image by digest); the previous config declaredversion: "2"but used v1 schema keys, so every threshold in it was inert and its green result was meaningless.backend/Makefile'slinttarget now asserts the config's sha256 against the canonical file first, so drift from the org standard fails the build instead of silently degrading to defaults - 2026-08-10: every interactive control now meets the 44x44 CSS px minimum tap
target (
.pin-btn,#interval-select, the debug-log label and, on narrow viewports,#pause-btn). The pin button's hit area grows via matching negative margins, so its layout footprint and row density are unchanged - 2026-08-10: per-host status line wraps below the 768px breakpoint instead of forcing horizontal page scroll at 320px
- 2026-08-09:
Dockerfile.backendreworked to the mandated Go multistage lint-stage pattern: separatelintstage on the hash-pinnedgolangci/golangci-lintimage,COPY --from=lintstage dependency,CGO_ENABLED=0static build driven byARG VERSION, and no moreCOPY .git - 2026-08-09: dotfile compliance — lifted
backend/.editorconfigto the repo root soroot = truecovers the frontend too, and replaced.gitignorewith the org model (OS, editor, node, and environment/secrets sections) plus this repo'sdist/and*.log..env,.env.*,*.pem, and*.keyare now ignored repo-wide, not just underbackend/. Excluding.gitfrom.dockerignorestays deferred: both images read git metadata at build time (COPY .gitinDockerfile.backend,git rev-parseinvite.config.js) - 2026-08-09: automated responsive-layout harness
(
make frontend-viewport-test): digest-pinned headless Chrome driven over CDP against the builtdist/, viewport widths derived from the breakpoints insrc/styles.css(#13). Every check carries a presence guard so none of them can pass against a page it is not actually measuring. Found two real layout defects, filed as #42 and #43 - 2026-07-07 Adopted scripts-to-rule-them-all:
script/entrypoints, Makefile shims, README Entrypoints section - 2026-02-27: backend with buffered zstd-compressed report storage; CI workflow and backend repo standard files; backend Dockerfile fixed (Go 1.25, golangci-lint) and moved to repo root (feat/reportbuf-storage)
- 2026-02-26: host row layout redesigned with CSS grid; overflow and spacing fixes; nginx config extracted; port hardcoded to 8080
- 2026-02-26: debug log panel, median stats, recovery probe, Docker build fix, S3 Singapore endpoint added
- 2026-02-23: summary box redesign, host pinning, local and UTC clocks, checks counter
- 2026-02-23: hosts sorted by latency; GET instead of HEAD for latency; timeout derived from interval; Hetzner regional endpoints; 3s interval
- 2026-01-29: initial NetWatch network latency monitor
Future Steps
- Wire
script/frontend-viewport-testinto CI as its own step (deliberately not part ofmake checktoday; the decision has real CI-runtime cost and is tracked separately) - Compliance top-up as one small commit: add .editorconfig and add the hooks target to the Makefile
- After merge, confirm .gitea/workflows/check.yml is on main and CI is green (main always green policy)
- Decide what to do with untracked resume.sh: commit it, gitignore it, or delete it
- Upstream fix needed in
sneak/prompts: the org-standard.golangci.ymlenablesgomodguard, which golangci-lint v2.12.2 reports as deprecated since v2.12.0 and replaced bygomodguard_v2, so every backend lint run prints a deprecation warning. The file is standardized and must never be edited in this repo, so nothing can be done here beyond tracking it — tracked at https://git.eeqj.de/sneak/netwatch/issues/41