mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-19 00:12:18 +00:00
chore: correct body-cap comments, dockerignore licence posture, stale log copy
- workouts/batch + safeJson: the body cap is a DoS ceiling, not a bound the worst-case payload always fits under; an extreme GPS-heavy backlog can exceed it and falls back to smaller batches client-side. Note that request.text() still buffers the raw body, so the cap bounds the parse cost, not the initial read. - .dockerignore: keep LICENSE / LICENSE.md in the image — AGPL-3.0 conveys with the software. - reminder-worker: the dense walk flag is an operator kill-switch now that the fold is reworked, not a pending-rework gate.
This commit is contained in:
1 parent
33358c7960
commit
8456d3bbc3
4 files changed
+24
-21
No files matched your search
+10
-7
@@ -201,13 +201,16 @@ export function apiError(
|
||||
* Returns the parsed body or a 400 error response if parsing fails.
|
||||
*
|
||||
* `opts.maxBytes` opts a route into a hard body-size cap. The check
|
||||
* runs against the raw text rather than the parsed object, so a
|
||||
* gigabyte payload never reaches `JSON.parse` and never lands in
|
||||
* heap. Single-record routes can pass a tight cap (a few KB); batch
|
||||
* routes that legitimately accept large payloads can pass a larger
|
||||
* one (a few hundred KB). When `maxBytes` is omitted the route
|
||||
* inherits the Next.js runtime default — pre-existing behaviour, no
|
||||
* regression risk for callers that haven't adopted the parameter.
|
||||
* runs against the raw text length rather than the parsed object, so an
|
||||
* over-limit payload returns 413 before reaching `JSON.parse` and never
|
||||
* builds an object graph. (`request.text()` still buffers the raw body
|
||||
* into a string, so the cap bounds the parse/object cost, not the
|
||||
* initial read — keep caps comfortably above the largest legitimate
|
||||
* payload.) Single-record routes can pass a tight cap; batch routes
|
||||
* that legitimately accept large payloads pass a larger one. When
|
||||
* `maxBytes` is omitted the route inherits the Next.js runtime default —
|
||||
* pre-existing behaviour, no regression risk for callers that haven't
|
||||
* adopted the parameter.
|
||||
*/
|
||||
export async function safeJson<T = unknown>(
|
||||
request: Request,
|
||||
|
||||
@@ -2824,7 +2824,7 @@ export async function startReminderWorker() {
|
||||
if (!DENSE_INTRADAY_RETENTION_ENABLED) {
|
||||
workerLog(
|
||||
"info",
|
||||
"[dense-intraday-retention] disabled — skipping the nightly walk (P2002 fold collision; re-enable via DENSE_INTRADAY_RETENTION_ENABLED once reworked)",
|
||||
"[dense-intraday-retention] disabled via DENSE_INTRADAY_RETENTION_ENABLED — skipping the nightly walk (operator kill-switch)",
|
||||
);
|
||||
} else {
|
||||
const denseSummary = await runDenseIntradayRetention(
|
||||
|
||||
Reference in new issue
Block a user