Files
HealthLog/tests/integration/routes/parity/__snapshots__/analytics.09-anonymous.json.snap
T
Marc-André Bombeck b2f6c37c37 test(kit): pin parity walks to today where a route reads the database clock
Some read routes cut their windows in SQL against the database's now(),
which a pinned Date cannot reach; a walk pinned to a fixed date then reads
less of its record every day the calendar moves on. relativeToAnchor writes
every instant and day key of a snapshot relative to the start of the
current UTC day, so a walk can lay its record out from today and still read
the same snapshot on any day.

The series walk uses it with the clock unpinned; the analytics walk pins
the clock to noon of today, keeps its account in UTC and is re-recorded in
that form (its earlier snapshots proved the builder move before this
change).
2026-10-23 14:09:41 +02:00

52 lines
1.0 KiB
Plaintext

{
"status": 401,
"cacheControl": null,
"body": {
"data": null,
"error": "Not authenticated",
"meta": {
"errorCode": "auth.missing",
"requestId": "<requestId>"
}
},
"events": [
{
"status": 401,
"action": null,
"meta": null,
"warnings": null,
"error": {
"type": "HttpError",
"message": "Not authenticated"
}
}
],
"effects": [],
"stored": {
"healthScores": [
{
"dayKey": "day+0",
"timezone": "UTC",
"composite": 86,
"band": "green",
"scoreVersion": 4,
"composition": [
"BLOOD_PRESSURE",
"GLYCAEMIA",
"ACTIVITY",
"SLEEP"
],
"pillarScores": {
"SLEEP": 92,
"ACTIVITY": 78,
"GLYCAEMIA": 100,
"BLOOD_PRESSURE": 73
},
"inputFingerprint": "5653cd8c051404182d6c6f813a48b1c2ebc3abe1116901466ab7cc1ab70cb276",
"computedAt": "anchor+0d+12:00:00"
}
],
"patterns": []
}
}