Fix the stale logging rule and drop go test from the README

This commit is contained in:
2026-09-08 20:18:52 +02:00
parent 8413f05f04
commit 9be4cd188a
2 changed files with 4 additions and 3 deletions
+3 -2
View File
@@ -71,8 +71,9 @@ This service runs in Kubernetes behind a TLS-terminating ingress.
- All upload code paths must enforce `maxUploadSize` via - All upload code paths must enforce `maxUploadSize` via
`http.MaxBytesReader`, and clean up any partially written file/directory `http.MaxBytesReader`, and clean up any partially written file/directory
on failure. on failure.
- New HTTP handlers must call `logRequest` with an accurate status code for - New HTTP handlers must write an explicit status code on every response
every response path. path. The `withLogging` middleware records what `responseRecorder` actually
saw, so a handler that returns without writing is logged as a 200.
- Keep the JSON error shape for `/upload` consistent with - Keep the JSON error shape for `/upload` consistent with
`writeMultipartError` (`{"error": "..."}`). `writeMultipartError` (`{"error": "..."}`).
+1 -1
View File
@@ -109,7 +109,7 @@ to write to whatever is mounted at `/uploads`.
## Development ## Development
```sh ```sh
go build ./... && go vet ./... && gofmt -l . && go test ./... go build ./... && go vet ./... && gofmt -l .
``` ```
Run locally: Run locally: