5 Commits

Include renames

Author	SHA1	Message	Date
sneak	397a47b529	Report file writes run one at a time (closes #150) ... Two writes that failed at the same time put their reports back in the wrong order when the older one failed first. A mutex is now held across each write, from taking the waiting reports out of the buffer to putting them back if the write fails, so the next write takes them in order. The write Append starts at the 10 MiB threshold waits for one under way, and Append starts no other while it waits. Files written since the start are now deleted to make room in the order they were written. A test that needed two writes at once is removed. Model: opus-5-5	2026-10-19 01:28:44 +00:00
clawbot	be6dc93eaa	Unusable DATA_DIR error names DATA_DIR; report file number is atomic.Int64 (closes #148, closes #161) ... When the backend runs on its own, a DATA_DIR that could not be created or read stopped the start with an error that named the path but not DATA_DIR, and one where no file could be created let it start, to fail at the first write of a report file. The start now creates a file in DATA_DIR and removes it, and all three cases fail with DATA_DIR "<value>": <reason>, the form config.New uses for the other settings. Tests start the buffer with DATA_DIR below a regular file and with DATA_DIR set to /proc. The report file sequence counter is atomic.Int64 instead of atomic.Uint64, as the Go style guide asks for int types. File names are unchanged. Model: opus-5-5	2026-10-19 03:15:35 +02:00
clawbot	2861be1c4d	Stopping the server waits for report file writes under way (closes #122) ... The report buffer's stop now waits, through a sync.WaitGroup, for flushLoop and for the write Append starts at 10 MiB before its final flush. It used to return at once, so the process exiting cut such a write off and its reports were lost. A write under way that fails puts its reports back in the buffer, so the final flush writes them; the stop fails only if that flush fails too. Tests hold the periodic write and the one at 10 MiB open in a synctest bubble 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. Model: opus-5-5	2026-10-14 14:47:01 +02:00
clawbot	cff7b07bbc	Reports refused while report files cannot be written (closes #123) ... A failed write of a report file used to drop its reports, and POST /api/v1/reports kept answering 200 for as long as writes failed. Now a failed write puts its reports back in the buffer, still counted against DATA_DIR_MAX_BYTES, and Append refuses every report, which the handler answers 500, until a write succeeds. The minute flush tries the held reports again, so storing resumes with no restart once writing works, and the buffer takes nothing new while writes fail. Tests also cover a report appended while a write that fails runs, and the cap once a failed write's reports are written. Model: opus-5-5	2026-10-14 13:47:14 +02:00
clawbot	406e073aee	Move to the layout REPO_POLICIES.md gives (closes #30) ... The Go module moves from backend/ to the root (go.mod, go.sum, .golangci.yml, cmd/, internal/), the page's source to web/, and nginx's two files to configs/. backend/ is gone: its LICENSE and .dockerignore are deleted, and its .gitignore entries, README and scripts are folded into the root ones. script/build builds the server binary after the frontend; script/run and script/clean move up from backend/script/; make test, lint, fmt and fmt-check do what the backend's did. Vite's root is web/ and it still builds into dist/. go.mod ignores node_modules/, whose npm packages can ship .go files. script/bootstrap no longer installs gcc, which only the host Go tests needed. Model: opus-5-5	2026-10-14 12:01:32 +02:00