mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-14 17:41:09 +02:00
5110065ebe
The SYNC_DEBUG.md runbook tries to inspect window.unifiedSync from DevTools to figure out why pending changes aren't flushing on mana.how. The script can't work because (a) the unified sync instance is never exposed on window and (b) the two most likely failure modes — push for an unknown appId, getToken() returning null — both `return` silently with no error, no telemetry, no state change. The pending count climbs and there's nothing in the console to point at the cause. This commit makes those failures visible: push() unknown appId When a pending change lands for an appId that isn't in the registered channels map (almost always a registry/migration drift like renaming an appId without migrating the existing pending rows) we now log a warning that names the offending appId, lists the known ones for comparison, and emits a push:error telemetry event with errorCategory='unknown-appid'. The pending rows for that appId would otherwise accumulate forever — same symptom as the SYNC_DEBUG report. push() no token getValidToken() can return null if the local exp check failed and the refresh-on-online retry didn't yield a new token. This was the silent path that was hardest to diagnose: the existing health-check telemetry only fires after a successful fetch, so there was no signal at all. We now log a warning, set channel.lastError = 'no-token', flip status to 'error' and emit push:error with errorCategory='no-token'. sync-telemetry.ts Widens the errorCategory union to include 'no-token' and 'unknown-appid' so the new emits type-check. getDebugInfo() New method on the createUnifiedSync return value. Returns a flat, JSON-serializable snapshot of every channel's state (status, online, clientId, serverUrl, channels[appId] with lastError + timer flags, plus knownAppIds at top level) so the SYNC_DEBUG runbook (Schritt C) can compare what the server is being asked to sync vs. what's actually sitting in _pendingChanges. (app)/+layout.svelte Exposes the live unified-sync instance on window.__unifiedSync in the browser. Not a security concern: every method on the returned object is also reachable via Dexie + a fresh fetch from the same DevTools console, and a malicious user can't escalate anything by poking at it. This is the global the SYNC_DEBUG Schritt C script needs to exist. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| calc/packages/shared | ||
| calendar | ||
| cards | ||
| chat | ||
| citycorners | ||
| contacts | ||
| context | ||
| docs | ||
| guides | ||
| inventory | ||
| mana | ||
| manavoxel | ||
| memoro | ||
| moodlit | ||
| mukke | ||
| news | ||
| nutriphi | ||
| photos | ||
| picture | ||
| planta | ||
| presi | ||
| questions | ||
| skilltree | ||
| storage | ||
| times | ||
| todo | ||
| traces | ||
| uload | ||
| zitare/packages/content | ||