netwatch/TODO.md

Workflow

• branch from next
• 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.md changes in the same commit as the work)
• push the branch and open a PR against next

Status

pre-1.0. No git tags. main is the stable branch and next the development branch, which every PR targets. The frontend and the Go backend ship as one Docker image, and the Gitea workflow .gitea/workflows/check.yml runs script/cibuild on every push, and cancels the older run on the same branch. Working toward 1.0.0.

Next Step

Run make frontend-viewport-test in CI as its own step; it is not part of make check, as it needs Docker and takes minutes.

Completed Steps

• 2026-10-19: netwatch-server starts the server only when given no arguments (#179). check-cidr CIDR and prepare-data-dir DATA_DIR behave as before; any other arguments, such as a subcommand with no value or two, or a misspelt one, print a one-line usage message naming both forms to stderr and exit 2. They used to start the server. Unit tests call cli.Main with no arguments and check that it starts the server, and with each subcommand given no value and two values and with a misspelt subcommand, and check the exit code, the message and that the server does not start
• 2026-10-19: main() in cmd/netwatch-server/main.go is one call into a new package, internal/cli, as the Go style guide asks (#160). internal/cli runs the check-cidr and prepare-data-dir subcommands, with the same arguments, messages and exit codes, and otherwise the server, with the fx wiring. Appname and Version stay in main, where the build sets Version, and main gives cli.Main stderr and the function that runs the server, which the tests replace with a buffer and a function that fails them. Unit tests call cli.Main with check-cidr and a CIDR the server takes and one it refuses, and check the exit code and what it writes to stderr, and with prepare-data-dir and a path outside /data, and check that it exits 1 with the error from looking up the netwatch user, which the test image does not have. Others give the functions behind the subcommands input they take and input they refuse, and check the exit code and what they write to stderr
• 2026-10-19: when VERSION is unset or empty, script/build stamps the version from git describe --tags --always --dirty, as script/docker does (#156). Without --tags it skipped lightweight tags, so make run could report a commit where the image built from the same tree reported the tag. Checked once with a lightweight tag on a scratch clone: make build stamped it
• 2026-10-19: .dockerignore keeps Go test binaries and coverage output at the root out of the build context, with /*.test and /*.out in the repository's own section (#155). Such files went into the build context of every docker build in script/ and were copied into the lint, test and build stages. Checked with a probe image that copies the whole context: x.test and x.out planted at the root no longer land in it, and nothing else changed. The entries match only at the root, so the same files in a subdirectory still reach the image
• 2026-10-19: .gitea/workflows/check.yml is the sneak/prompts copy at 0653579 (#153). Its checkout step sets fetch-depth: 0, so CI clones all history and tags, and git describe in script/cibuild gives the image built from a tagged commit the tag as its version; it gave the short commit. The checkout step also sets persist-credentials: false, so the job's token is not left in .git/config. A new push cancels the older run on the same branch, and a run stops after 20 minutes
• 2026-10-19: script/bootstrap keeps the yarn on PATH only when yarn --version is exactly YARN_VERSION, and otherwise installs that version as it did when no yarn was installed (#154); any yarn used to be kept. It uses the node on PATH only when that node has the major version of NODE_VERSION, as REPO_POLICIES.md asks, and is at least NODE_MIN_VERSION; a node 24 was kept before. After installing node or yarn it looks the tool up through PATH again and stops if that one fails the same check, as it does for Go, and it prints the node and yarn versions it uses. Every script that runs yarn on the host, except script/bootstrap, which picks its own node and yarn, runs it through the new script/yarn. That script puts ~/.local/bin first on PATH, uses the first node on that PATH when it passes the same test, and otherwise runs yarn under the pinned node in nvm; make build ran yarn under whatever node was first on PATH
• 2026-10-19: bin/entrypoint.sh has each of its steps in a function, and a main at the end calls them in order, as the shell section of the code style guide asks (#163). It is still POSIX sh with no set -e, and does what it did, with the same messages and exit codes. Checked by running the image with each script: a normal start, bad PORT, TRUSTED_PROXIES and DATA_DIR values, docker stop, INT, and nginx exiting on its own
• 2026-10-19: while report files cannot be written, the health check answers 503 with "status":"error" and the same fields, so the image's HEALTHCHECK reports the container unhealthy (#142). It answered 200 "status":"ok" whatever happened, so the platform saw a healthy container while every report was refused with 500. It answers 200 at start, before any write has failed, and again from the first write that succeeds. A unit test removes DATA_DIR to make a write fail and checks the 503, then puts it back and checks the 200 after the next write
• 2026-10-19: report file writes no longer overlap (#150), so the reports of failed writes are written in the order they arrived. Two writes that failed at the same time put their reports back in the wrong order when the older failed first. One write runs at a time, and each takes the waiting reports only when it starts, after a failed write has put its own back. The write Append starts when 10 MiB are waiting waits for any write under way, and Append starts no other while it waits. Files written since the start are deleted to make room in the order they were written, after those found at start. A unit test holds a write open, starts a second at 10 MiB, fails both and checks the order in the next file. Others check that Append starts no second write at 10 MiB while one waits, that it starts one again the next time 10 MiB are waiting, and that the first file written since the start is the first deleted
• 2026-10-19: DEBUG unset or empty leaves debug logging off, and any other value, false and 0 included, turns it on, as the code style guide says (#159). No value of it stops the start any more; before, only 1, t, T, TRUE, true, True, 0, f, F, FALSE, false and False were accepted. README.md no longer gives false as its default
• 2026-10-19: check builds keep Go's modules and compiled packages between runs (#118), on sneak's rulings in prompts#113 and prompts#130. REPO_POLICIES.md, script/test, script/lint, script/docker and script/cibuild are the sneak/prompts copies at 0653579: the scripts pass a new CACHEBUST value where they passed --no-cache, and the lint and test builds write no image. In each stage of Dockerfile, ARG CACHEBUST comes after the system packages and the Go module download, and before every step that lints, tests or compiles and the node stages' yarn install. Go's build cache and golangci-lint's are cache mounts, and both go test runs carry -count=1. The test phase's Go caches used to be in memory, empty on every build
• 2026-10-19: the three unit tests of a check whose result is discarded (its round given up, the user paused, or the first round) also check that the host's history is still empty, its status still pending, and nothing was written to the console (#151). They checked only the row, so a change that recorded the result and skipped only the row would have kept them passing
• 2026-10-18: when the backend runs on its own, a DATA_DIR that cannot be created or read, or where no file can be created, stops the start with an error naming DATA_DIR and its value, as the other settings' errors do (#148); the first two named only the path, and the third was found only at the first write of a report file. At start the server creates a file in DATA_DIR and removes it. Unit tests start the buffer with DATA_DIR below a regular file and with DATA_DIR set to /proc, and check the error. The report file number is an atomic.Int64, as the Go style guide asks for int types (#161); file names are unchanged
• 2026-10-18: the image's nginx sends the page with Cache-Control: no-cache (#141), so a browser that keeps a copy checks with the server that it is current before using it again. The page went out with no Cache-Control, so a browser could keep it after a deploy and ask for files under /assets/ that the new build no longer has, and show an empty page. A path that location / answers with the page through its try_files fallback gets the same header. location / now includes the security headers again, as /assets/ does, since its own add_header drops the server's. /assets/ keeps its immutable caching. make frontend-viewport-test fails unless / and a path that falls back to the page carry Cache-Control: no-cache and Content-Security-Policy, which comes from the same file as the other security headers
• 2026-10-18: README.md says what the page loses while reports are refused or the page is paused (#145), how fast one address can replace the stored reports (#146), and that in the image nginx answers a body over 1 MiB itself (#147). A sample in the history that no report has delivered is sent only as long as the history holds it: at the 1-second interval one refused or failed report loses the oldest 20 seconds of each host's samples, and a pause longer than the history loses every sample between the last delivered report and the pause. Samples an interval change cleared are kept apart, the last 100 per host, until they are delivered. At the defaults, one address sending 1 MiB reports made up to compress badly can fill the 1 GiB cap in about 17 minutes. nginx's client_max_body_size is also 1 MiB by default, so in the image it answers a larger body with 413 and its own HTML page, and the backend never sees or records it; the backend's own 413 sentences now say they apply to it run on its own. The reporter, the body limit and nginx are unchanged
• 2026-10-18: a browser that cannot format the header's clocks still probes (#149). The clocks name the local time zone through Intl.DateTimeFormat's shortGeneric option, which Chrome before 95, Firefox before 91 and Safari before 15.4 reject with an error; it came before the first round started, so such a browser never checked a target. The clocks now start last, after the rounds, and an error formatting them leaves both blank. The footer's color legend reads >=500ms for red, where it read >500ms, so 500 ms, which is red, is in one of its colors (#152). Unit tests check the clocks with a working Intl.DateTimeFormat and with one that rejects shortGeneric, and draw the page and check the legend against every entry of CONFIG.latencyColors
• 2026-10-18: netwatch-server prepare-data-dir no longer changes the owner of a file outside /data through a hard link in the volume (#143). A file with a second name (hard link) keeps its owner, and the start logs its path. Owners are now set on the opened directory, file or link, never by name, so a hard link swapped in after the check is caught too; a symbolic link is opened without following it and given to the netwatch user itself, so the server can still follow one in a sticky directory that anyone can write to. Devices, named pipes and sockets keep their owner. Setting the owner on an open file that is not a directory is built only for Linux: prepare-data-dir runs only in the Linux image, and macOS, where the backend is also built for development, has neither O_PATH nor AT_EMPTY_PATH. On any other system the package still builds, and prepare-data-dir fails at the first file that is not a directory. The test that runs as root hard-links a file, a symbolic link and a named pipe from outside the volume into it and finds their owners unchanged
• 2026-10-18: from a trusted proxy, the backend takes the client address from the right-most X-Forwarded-For entry that is not in TRUSTED_PROXIES (#144). It took the left-most entry, which the client writes itself behind a proxy that appends to the header, so a client could choose the address the rate limit counts and the request log records. An entry written as an address with a port is read as that address. With only trusted addresses in the header, or an entry that is not an address at all (such as unknown) met on the way, the direct peer is used. X-Real-IP is read only without X-Forwarded-For, and every X-Forwarded-For header line is read, not only the first. The image's nginx, and the TRUSTED_PROXIES=127.0.0.1/32 it starts the backend with, are unchanged; the comment in configs/nginx.conf that said the backend takes the first entry now says it takes the one address nginx passes on. Unit tests resolve the address from chains ending in an untrusted address, in trusted ones, of only trusted ones, with ports, with an entry that is not an address, and split over two header lines
• 2026-10-18: after an interval change, the summary's Reachable slot reads --/-- in white, as at page load, until the second round since the change ends (#140). It used to read 0/26 in red from the change on, as no WAN host had a check recorded, for up to two intervals with the network fine. The summary update now writes --/-- while every WAN host still waits for its first check. A unit test resets the hosts as the interval menu does and checks the slot; another checks that it reads 0/26 in red once every WAN host's check has failed
• 2026-10-14: stopping the server waits for a report file write already under way, the periodic flush's or the one Append starts when 10 MiB are waiting, before the final flush (#122). It used to return at once, and the process exiting cut the write off, losing its reports. A write under way that fails puts its reports back in memory, so the final flush writes them; the stop fails, and the process exits non-zero, only if that flush fails too. Two tests hold the periodic write and the one at 10 MiB open and find the stop waiting until each is released; a third makes the held write fail and finds its report written by the final flush. They run in a testing/synctest bubble, so the periodic flush comes without waiting a minute
• 2026-10-14: make test no longer runs the frontend's production build, which the tests do not need (#118). yarn build moved out of the stage that runs the frontend's unit tests, now named frontend-test, into a new frontend-build stage, which starts from it and, like the builder stage, waits on the lint and test phases, so the image still cannot be built unless they pass. The runtime stage copies dist/ from it, and the git that vite.config.js reads the commit with is installed there. No build cache was added
• 2026-10-14: opening the debug log no longer raises the measured latencies (#131). With the panel open, each line written drew the panel again with every line before it, up to 1000, and a check that ends while the page draws is timed only when the drawing is done. Each line is now added at the end of the open panel, its first line is dropped once it holds more than 1000, and it scrolls to its newest line once a frame rather than once a line; the whole panel is drawn only when it is opened. A unit test writes more lines than the panel keeps and checks that the lines already shown are left as they are
• 2026-10-14: unset, the backend's own TRUSTED_PROXIES trusts 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16, and no longer loopback; a list replaces that; set and empty, it trusts no proxy, where it used to get the default, as viper reads an empty environment variable as unset (#129). A value it cannot parse still stops the start, and the image still starts the backend with TRUSTED_PROXIES=127.0.0.1/32. Tests load the config with it unset, empty and set to a list
• 2026-10-14: while report files cannot be written, POST /api/v1/reports answers 500, and storing recovers once writing works again, with no restart (#123). A failed write puts its reports back in the report buffer, still counted against DATA_DIR_MAX_BYTES, where they used to be lost; the next flush, within a minute, tries them again. Until a write succeeds, every report is refused and nothing of it is kept, so the buffer does not grow while writes fail. A test posts reports through the report handler before, during and after a failure; others check that a report appended while a write runs is kept, behind that write's own, when the write fails, and that the cap still holds exactly once a failed write's reports are written
• 2026-10-14: a request whose handler panics is logged with status 500 and counted with code 500 in the metrics (#125), not 200. Recoverer is still the first middleware; Write500OnPanic, after the request log and after the metrics, writes the 500 as the panic passes and lets it go on to Sentry and Recoverer, which now writes a 500 only when no status was written
• 2026-10-14: with TRUSTED_PROXIES unset, the container's nginx trusts the three private ranges of RFC 1918, 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 (#119), as sneak ruled on 2026-09-22 for every app; it trusted no proxy before. A list replaces them, and set and empty it trusts none. The backend inside the container still trusts only 127.0.0.1/32
• 2026-10-14: POST /api/v1/reports takes only a report sent with Content-Type: application/json, parameters such as charset allowed, and refuses any other with 415 and the usual error body, storing nothing (#126). A page on another origin can send a text/plain POST without a CORS preflight, so any site could make its visitors' browsers store reports; a JSON POST waits for the preflight, which only an origin in CORS_ALLOWED_ORIGINS passes. The page already sent application/json. A test posts a report as text/plain, as application/x-www-form-urlencoded, as multipart/form-data, with no Content-Type, and as application/json with and without a charset, and checks which are stored
• 2026-10-14: changing the interval no longer drops the samples not yet reported to the backend (#124). The interval menu resets each host with the new HostState.reset, which moves the history's entries to clearedHistory, keeping the last 100 of all it has cleared, and buildReport reads both, so the next report has the samples recorded before the change that no report has delivered. Until its next check, such a host is sent with the status of its last check, not pending. The page's history still starts over, and the per-host marks still leave out of a report the samples a delivered one had. Unit tests reset a host as the interval menu does and find its unreported samples in the next report, and only the last 100 after more were cleared; web/src/main.js now exports Reporter for them
• 2026-10-14: the repo has the layout REPO_POLICIES.md gives (#30). The Go module is at the root (go.mod, go.sum, .golangci.yml, cmd/netwatch-server/, internal/), so its path sneak.berlin/go/netwatch names the repository. go.mod ignores node_modules/, where npm packages can ship .go files that make tidy would otherwise read as this module's packages. The page's source is in web/ (index.html, src/), which vite.config.js makes Vite's root; the build still goes to dist/. nginx.conf and security-headers.conf are in configs/. backend/ is gone: its LICENSE and .dockerignore are deleted, its .gitignore entries are in the root one, its README.md is folded into the root README.md, and its scripts into the root script/: script/build builds the server binary after the frontend, script/run and script/clean came from backend/script/, and make test, make lint, make fmt and make fmt-check do what its test, lint, fmt and fmt-check did. script/bootstrap no longer installs gcc, which only the host Go tests needed. The image and the page are unchanged
• 2026-10-07: the files shared from sneak/prompts are its copies at commit dd4027b (#113), with this repository's own entries after the shared content in .gitignore, .dockerignore and .editorconfig. make lint and make test each build one phase of Dockerfile without the cache: lint runs golangci-lint v2.14.0 over backend/ and, through the frontend-lint stage, eslint; test runs the Go tests on the Debian Go image and, through the frontend stage, the frontend's unit tests and build. The builder stage waits on both, and without a VERSION build argument takes the version from git describe on the .git in the build context. Neither linter nor the tests run on the host for make check; backend/script/lint runs the root one, and backend/.golangci.yml is no longer checked against a sha256. prettier formats only the JavaScript, CSS, HTML and Markdown, so the shared .golangci.yml stays as fetched. script/fmt and script/fmt-check put ~/.local/bin on PATH, which the shared workflow no longer does. script/frontend-lint and script/frontend-check are gone
• 2026-10-07: the six Hetzner targets answer again, and failed checks are written to the browser console (#114). The Hetzner speed-test servers close the connection without an answer when the URL has a query string, and every check added ?_cb= and the time; checks now fetch each target's URL as written, with cache: 'no-store' as before. Each recorded check that fails writes one console.error line, and the same line to the debug log, with the target's name and URL, the time, what failed and how long the request took; a target that answers after failed checks writes one console.info line. Checks the page does not record write none, so the debug log no longer lists failures in the first round or in the recovery probe
• 2026-10-04: the page's footer no longer says "IPv4 only" (#111): each check is a fetch, the browser picks IPv4 or IPv6 for each WAN host, and the local targets are IPv4 addresses. The rest of the footer is unchanged
• 2026-10-04: README.md, TODO.md and test/viewport/README.md say what the tree does (issue #24). The README's Getting Started leads with make targets; a new Backend section says what netwatch-server stores, its routes and how the image builds and runs it, and points to backend/README.md for its settings; the checks are GET requests; the 26 WAN hosts, the four health states, the summary's figures and the features the list lacked are described as the page has them; and its TODO section points here, as does the one in backend/README.md, whose open items moved to Future Steps. This file's Workflow branches from next and opens the PR against next, Status says where the repo stands, and Next Step and Future Steps hold only open work, linked to its issue where one exists. The viewport harness README names Node's test runner, not vitest
• 2026-10-04: in src/main.js (issue #102), a target's min, max, median and average latency come from one list of its answers, through the same function the summary's figures use, so the median is written once. The latency color limits are one table in CONFIG, read by both the figure's and the sparkline's color. The health thresholds, the debug log's length, the gateway check's timeout, the recovery probe's number of hosts and interval, how often the rows are sorted and the delay before the first sparkline resize are CONFIG entries too. A unit test checks the summary's figures. Nothing the page does or shows changed; the footer's color legend still writes the limits out as text
• 2026-10-04: password guesses at /metrics are rate limited (issue #104): each client address, resolved through TRUSTED_PROXIES as for reports, may make 60 requests to /metrics a minute, counted by go-chi/httprate apart from its reports; past that it gets 429 and its basic auth credentials are not checked. The limit is a constant in backend/internal/server/routes.go. A test uses up one client's allowance on wrong passwords, gets 429 with the right one, and checks that another client behind the same nginx still gets in
• 2026-10-04: the backend reports errors to Sentry (issue #95). With SENTRY_DSN set, it sets up sentry-go with the release netwatch-server- and its version, reports each panic in a handler through sentryhttp, the last of the middleware every request goes through, which panics again so the request still gets the 500 from the panic recovery, and waits up to 2 seconds on shutdown for Sentry to finish sending. A DSN Sentry refuses stops the start with an error naming SENTRY_DSN. With it empty, Sentry is not set up and nothing is sent to it
• 2026-10-04: a target's name and URL and a debug log message show as the characters they are and are never read as HTML (issue #29): a host row escapes the name and URL it writes into its markup, and the debug log sets each line as text. A unit test checks a target whose name and URL hold <, >, ", & and '. README.md no longer calls CONFIG frozen: the interval menu sets its updateInterval, and the values computed from it follow. AppState declares the recovery probe's two properties, the sparkline axis functions lose the parameters they did not use, and the comment on a target's history names both kinds of entry it holds. Nothing the page does changed
• 2026-10-04: a dependency can be added without running yarn or go by hand (issue #45): make add-dependency PACKAGE=<name>@<version> shims to the new script/add-dependency, which runs yarn add --dev, so package.json and yarn.lock change together, then yarn install --frozen-lockfile; the same command moves a package to another version. make tidy shims to the new script/tidy, which runs go mod tidy in backend/: a Go module is added by importing it, or moved by editing its require line, then make tidy. script/bootstrap still installs with --frozen-lockfile
• 2026-10-04: the backend serves Prometheus metrics (issue #94). With METRICS_USERNAME and METRICS_PASSWORD both set, it records request duration and response size through go-http-metrics and serves them, with Go's runtime and process metrics, at GET /metrics behind basic auth with those credentials; nginx passes /metrics to it as it does /api/. With neither set there are no metrics and /metrics is 404; one without the other stops the start with an error naming both, and so does a METRICS_USERNAME containing :, with an error naming it. Only requests that reach the health check or POST /api/v1/reports are recorded, not /metrics itself and not every request as GO_HTTP_SERVER_CONVENTIONS.md shows, because the labels are the request's path and method, which clients can make up without end. For that, POST /api/v1/reports is now registered by its full path instead of inside a /api/v1 route group; it answers as before
• 2026-10-04: script/ and Makefile follow the org models (issue #28): make dev shims to the new script/dev, the Vite dev server, and the new make build to script/build, the frontend production build. .prettierignore no longer leaves out backend/, so make fmt and make fmt-check cover backend/README.md; it leaves out backend/.golangci.yml by name, the org standard file whose sha256 backend/script/lint checks. script/install-precommit and the date on script/bootstrap's pins are the org model again; script/bootstrap, script/fmt and script/fmt-check each say in a comment why they differ from it
• 2026-10-04: a frontend build on Node 26 or newer, such as make test on a host with Node 26, no longer prints Node's warning that module.register() is deprecated (issue #32); the build in Dockerfile runs on Node 22, which never printed it. The call was in @tailwindcss/node, which @tailwindcss/vite brings in at its own exact version; tailwind 4.3.1 calls module.registerHooks() instead where Node has it. yarn.lock now has @tailwindcss/vite and tailwindcss at 4.3.3, inside the ranges package.json already allowed, and tailwind's own dependencies moved with them. The built CSS changes only in how it is written out, in tailwind's Firefox focus-ring rule, which no longer applies to iframes (the page has none, so nothing on it looks different), and in tailwind's default sans-serif font list, which the page does not use: body sets a monospace font
• 2026-10-03: the frontend's unit tests cover what the page computes (issue #21): humanDuration, the latency colours of a figure and of a sparkline either side of each boundary, a target's min, max, average and median latency over an empty history, an all-unreachable one and a mixed one, and each of the four health states either side of its thresholds. package.json has a test script, so yarn run test and npm run test run them, and script/frontend-test runs it: quietly, and if a test fails, again with every test listed, and then fails. src/main.js now exports humanDuration, HostState, latencyClass and latencyHex for the tests; nothing it does changed
• 2026-10-03: the backend's logs are one stream (issue #27): fx logs its own steps of starting and stopping through the backend's logger, so off a terminal every line the backend's own logger and fx write is JSON, where fx used to write plain text to stderr. A config file that is found but cannot be read now stops the start with its error, logged as JSON like a bad setting, where it used to end in a Go panic. A test runs the server as a child process and checks both. The backend logs its name, version and architecture once at start. The health check's uptime keys are now uptime_seconds and uptime_human; its path, content type, "status":"ok" and 200 are unchanged. SENTRY_DSN, METRICS_USERNAME and METRICS_PASSWORD are still read and still unused, and left out of backend/README.md, until issues #94 and #95 wire them up
• 2026-10-03: the frontend has a real linter (issue #47, and item 2 of issue #28): eslint with its recommended rules, set in eslint.config.js, runs in a new frontend-lint stage of Dockerfile, which the frontend stage waits on, as the builder stage waits on the Go lint stage. script/lint builds both stages without the cache and runs no linter on the host. script/frontend-lint runs eslint where it used to repeat the prettier check that script/fmt-check runs on the host, and script/frontend-check, run by the frontend stage, is now the tests and the format check. script/bootstrap wants node 22.13.0 or newer, as eslint 10 does
• 2026-10-03: the tap-target check in make frontend-viewport-test expects one visible pin button per WAN host row (issue #46), where it expected at least 10 of the 26, so pin buttons missing from only some rows now fail it. The host row count the harness gathers, which the app-rendered check also reads, now counts only the WAN host rows: the local host rows have no pin button
• 2026-10-03: each target's row shows its result as soon as its check ends (issue #91), where every row waited for the round's slowest check, up to 24 seconds at a 30-second interval. Every row is still redrawn, and sorting, the summary, the health box and offline detection still run, once, when the round's last check ends, so no row reads "paused" after a pause and resume during the round. A check that ends after the user pauses or after its round is given up shows nothing, and the first round is still discarded as a whole
• 2026-10-03: root no longer acts outside /data when it prepares DATA_DIR (issue #80): bin/entrypoint.sh runs netwatch-server prepare-data-dir, which refuses a DATA_DIR that is not /data or a path below it written in full, then creates DATA_DIR, gives /data and everything in it to netwatch and sets the modes, all through a Go os.Root opened on /data. That refuses any path leading out of /data, so neither a symbolic link already there nor one a host process swaps in during the start can make root create or change anything elsewhere, and DATA_DIR=/etc no longer gives /etc to netwatch. The README.md section "Running under upaas" says which values are accepted
• 2026-10-03: DATA_DIR_MAX_BYTES is now how much of the report files is kept (issue #54): when a report would take them past it, the oldest report files are deleted to make room, each deletion logged, and at start files already past it are deleted the same way. A file still being written is never deleted. A report is refused with 507 only when the reports waiting to be written fill the cap on their own, and then no file is deleted. The reports of a failed write stop counting, and the part of its file written is removed. A file that cannot be deleted still counts until the next start; one already deleted by hand counts as freed
• 2026-10-03: backend/script/lint says what went wrong with its .golangci.yml check (issue #34). On a hash mismatch it says to compare the file with the org standard: if they differ, restore the org standard; if they are the same, the org standard changed, so update GOLANGCI_CONFIG_SHA256 in that script. It used to say only to restore the file, which loops once the org standard itself has moved. A missing .golangci.yml, and a sha256sum that is missing or prints no hash, each get their own message instead of being reported as a mismatch; every one still fails the lint
• 2026-10-03: the Go tests run with the race detector and coverage (issue #88): backend/script/test runs go test -timeout 30s -race -cover ./... and, if that fails, runs it again with -v and fails. Go's -timeout bounds the tests, not their compile; the root script/test no longer puts one 30-second timeout around both halves, which a cold Go build cache could use up on compiling alone. The race detector needs a C compiler: the builder stage of Dockerfile has gcc and musl-dev, and script/bootstrap installs gcc, with the C library headers on apt and apk, when gcc is missing; the binary is still built with CGO_ENABLED=0. New tests cover the health check's answer, a valid report's answer, a report file's exact contents, and the flush when the buffer reaches 10 MiB; the handlers' TestImport stub is gone
• 2026-10-03: each target check times out after 80% of the refresh interval (issue #78), 24 seconds at 30 seconds, where it was capped at 3 seconds. A round started early, after an interval change or when the recovery probe finds a target answering, gives up the last round's checks if they are still waiting, so rounds never overlap; the recovery probe gives up its own checks after half a second. The frontend has its first unit tests, run by script/frontend-test with Node's built-in test runner; for them, index.html now links src/styles.css, which src/main.js used to import
• 2026-09-29: the container sets up its own data directory (issue #75): bin/entrypoint.sh, still as root, creates DATA_DIR if missing and gives it and /data to the netwatch user with mode 750 before starting the backend as that user, so an empty host directory owned by root, or one holding files from another uid, works with no step on the host. It stops the start instead when a symbolic link is on the path to DATA_DIR, since root would change whatever the link points to. The README.md first-run step that created and chowned the host directory is gone, and the image no longer sets that ownership at build time
• 2026-09-29: CI can no longer pass on checks that did not run (issue #37): script/cibuild is now the org model, byte for byte. It runs script/bootstrap and script/check, then builds the image with --no-cache and the version from git describe as the VERSION build argument, where it used to be a plain docker build . whose check steps could come from the build cache. The workflow puts ~/.local/bin, where bootstrap links what it installs, on the step's PATH, and bootstrap now installs its pinned node when the installed one is older than the frontend's dependencies need
• 2026-09-29: backend/.golangci.yml re-vendored from sneak/prompts (issue #41): gomodguard, deprecated in golangci-lint v2.12.0, is disabled and its successor gomodguard_v2 enabled with the org block list, so lint runs print no deprecation warning. The new file also turns depguard on with its test-support rule, which keeps net/http/httptest out of non-test code; netwatch adds no entries of its own to that rule. backend/script/lint checks the new sha256
• 2026-09-29: nginx sends the security headers REPO_POLICIES.md requires on every response (issue #18), including errors, /assets/ and what it passes on from the backend, whose own copies it drops so each header goes out once. They live in security-headers.conf, which nginx.conf includes. The content security policy allows no inline script or style, so the status dot's grey in src/main.js is now a class; connect-src is * because probed hosts redirect to others, and the browser checks each redirect against it
• 2026-09-29: the request log is bounded (issue #60): the method, URL, protocol, User-Agent, Referer, request ID (which chi takes from the client's X-Request-Id header) and client address it writes are each cut to 128 bytes, the bound the report handler already used, so one request can no longer put about 1 MiB per field into a log line. That bound and its helper now live in the logger package, shared by both
• 2026-09-29: nginx takes the client address from X-Forwarded-For only on requests from the reverse proxies named in the container's TRUSTED_PROXIES (issue #64), and by default from none, where it trusted every RFC1918 address before, so a client could write a new address on each request and escape the rate limit. bin/entrypoint.sh writes one set_real_ip_from line per entry into /etc/nginx/trusted-proxies.conf, which nginx.conf includes, refusing an entry that is not an IP address or CIDR, as netwatch-server check-cidr finds; it starts the backend with TRUSTED_PROXIES=127.0.0.1/32, since nginx is its only client
• 2026-09-29: report file names can no longer collide (issue #61): each is reports-<timestamp>-<number>.jsonl.zst, where the number goes up by one for each file the server starts to write, so two flushes in the same millisecond, such as a flush for size and the final flush at shutdown, each get a file of their own instead of the second one failing. A failed write uses up its number, leaving a gap if the file could not be created and otherwise a file under that number that may be incomplete.
• 2026-09-29: ready to run under upaas (issue #59): the image has a HEALTHCHECK that requests /.well-known/healthcheck through nginx on the port from PORT. The backend no longer reads a bad PORT as 0 or a bad DEBUG as false: those, and a BIND_ADDRESS that is not an IP address, stop it from starting with an error naming the variable, as the limits, CORS_ALLOWED_ORIGINS and, now by name, TRUSTED_PROXIES already did. bin/entrypoint.sh also refuses a PORT outside 1 to 65535, and 8081, where the backend listens inside the container, naming PORT. README.md has a "Running under upaas" section, whose first-run steps create the host directory for /data owned by uid 1000; the image does not change its owner
• 2026-09-29: nginx listens on PORT (issue #26), 8080 when unset or empty: the nginx image renders nginx.conf as a template at container start, filling in PORT and no other variable. bin/entrypoint.sh refuses to start when PORT is not digits only. server_tokens off keeps the nginx version out of responses. script/frontend-viewport-test renders the template the same way. Gzip and a 50x.html error page are not added
• 2026-09-29: bounded the report endpoint (issue #20): POST /api/v1/reports still needs no credentials, but each client address, as resolved through TRUSTED_PROXIES, may send REPORTS_PER_MINUTE (default 60) reports a minute, counted by go-chi/httprate, and past that gets 429 with Retry-After; the report files in DATA_DIR, counted from start with those already there, may total at most DATA_DIR_MAX_BYTES (default 1 GiB), past which reports get 507; and the wildcard CORS is gone: no CORS headers unless CORS_ALLOWED_ORIGINS lists origins, and an entry that is not a plain scheme://host[:port] origin, * included, stops the server from starting. Deleting report files frees room only at the next start; pruning is issue #54
• 2026-09-28: one container image (issue #52): the root Dockerfile builds the only image, and Dockerfile.backend is gone. nginx serves the frontend on port 8080 and proxies /api/ and /.well-known/healthcheck to the backend, which listens on 127.0.0.1:8081 in the same container; the new BIND_ADDRESS setting sets its listen address. bin/entrypoint.sh starts both, passes TERM and INT on to both, and exits non-zero when either exits on its own. The backend runs as user netwatch and stores reports on the /data volume. script/docker is the org model again
• 2026-09-28: unified the gate (issue #16): the root make check covers the Go backend as well as the frontend, and the pre-commit hook with it; the backend moved onto scripts-to-rule-them-all (backend/script/*, backend/Makefile as shims, its duplicate hook installer removed); script/cibuild builds both images and is the workflow's only build step. The root make lint runs golangci-lint only in Docker, by building the lint stage of Dockerfile.backend without the cache. script/bootstrap installs the pinned Go unless the installed one is at least what backend/go.mod asks for, links what it installs into ~/.local/bin without replacing anything it did not create, and installs no linter. Root make test runs both halves within one 30-second timeout. When VERSION is unset or empty, the backend binary's version falls back to git describe inside a git checkout, then to dev
• 2026-09-28: frontend reporting client (issue #53): a Reporter class posts collected samples to /api/v1/reports every reportInterval (default 60s) as a per-host delta, with the report-building step a pure exported function of host state; a per-host mark advances only on a delivered POST; at most one report POST is pending at a time and it is abandoned after half the interval, so a slow POST never overlaps the next report and a mark never moves backwards; the samples of an abandoned POST are sent again at the next interval, so a backend that stored them but answered late receives them twice; the per-browser client id works in insecure (plain-HTTP) contexts; vite.config.js proxies /api to the local backend for yarn dev
• 2026-09-28: report ingest correctness (issue #23): a storage failure now returns 500 instead of a false ok; oversize bodies return 413 (distinguished from malformed JSON, which stays 400); a MaxBodyBytes middleware caps every route, not just the report route; the raw attacker-controlled geo blob is no longer logged (only its length), and client_id, timestamp and decode error text are length-bounded before logging; a decodeJSON handler helper was added; panic recovery now routes the stack through slog instead of chi's plain-text stderr; and writing a report file now returns its error, so a failed final flush on shutdown makes the process exit non-zero instead of losing the buffered reports silently
• 2026-09-21: shutdown lifecycle correctness. The process now shuts down through fx instead of os.Exit, so every component's OnStop runs and buffered reports are flushed to disk on SIGTERM — previously a full flush window of telemetry was silently lost on every restart. The http.Server is now built before its serving goroutine starts, so shutdown can no longer race or nil-deref it; a listen failure exits non-zero via fx.Shutdowner; reportbuf OnStop is idempotent; and writeTimeout now exceeds the chi per-request budget so that budget is actually reachable. Dead startupTime, exitCode, and cancelFunc fields were removed
• 2026-09-21: backend HTTP hardening (issue #19): added ReadHeaderTimeout and IdleTimeout to the server, a SecurityHeaders middleware (HSTS, tight CSP, frame/sniff/referrer/permissions headers) registered before CORS, and trusted-proxy client IP resolution honouring X-Forwarded-For / X-Real-IP only from a TRUSTED_PROXIES allowlist (loopback plus RFC1918 by default)
• 2026-08-10: adopted the org-standard backend/.golangci.yml verbatim and moved the pinned golangci-lint from v2.7.2 to v2.12.2 (the lint stage of Dockerfile.backend now pins the golangci/golangci-lint:v2.12.2 image by digest); the previous config declared version: "2" but used v1 schema keys, so every threshold in it was inert and its green result was meaningless. backend/Makefile's lint target 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.backend reworked to the mandated Go multistage lint-stage pattern: separate lint stage on the hash-pinned golangci/golangci-lint image, COPY --from=lint stage dependency, CGO_ENABLED=0 static build driven by ARG VERSION, and no more COPY .git
• 2026-08-09: dotfile compliance — lifted backend/.editorconfig to the repo root so root = true covers the frontend too, and replaced .gitignore with the org model (OS, editor, node, and environment/secrets sections) plus this repo's dist/ and *.log. .env, .env.*, *.pem, and *.key are now ignored repo-wide, not just under backend/. Excluding .git from .dockerignore stays deferred: both images read git metadata at build time (COPY .git in Dockerfile.backend, git rev-parse in vite.config.js)
• 2026-08-09: automated responsive-layout harness (make frontend-viewport-test): digest-pinned headless Chrome driven over CDP against the built dist/, viewport widths derived from the breakpoints in src/styles.css (#13). The tap-target and host-row checks each fail when they measured nothing; the overflow, viewport-edge and clipped-text checks have no such guard of their own and rely on the app-rendered check, which fails the run when the app did not render. 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

• A backend test that posts a report to POST /api/v1/reports and checks the compressed file it is written to
• A backend route that decompresses the stored reports and answers queries on them
• Prometheus metrics for the backend's in-memory buffer: its size, the number of flushes and the number of reports
• A configurable host list (an environment variable or a config file)
• Export of the latency history (CSV or JSON)
• A notification when the health status changes to DEGRADED