Skip to content

fix(4d): §GANTT_CACHE_ERR_STACK — log the stack, the message alone cannot locate it - #1318

Merged
red1oon merged 2 commits into
mainfrom
fix/gantt-cache-err-stack
Sep 2, 2026
Merged

fix(4d): §GANTT_CACHE_ERR_STACK — log the stack, the message alone cannot locate it#1318
red1oon merged 2 commits into
mainfrom
fix/gantt-cache-err-stack

Conversation

@red1oon

@red1oon red1oon commented Aug 12, 2026

Copy link
Copy Markdown
Owner

Live on Hospital: §GANTT_CACHE_ERR Cannot read properties of undefined (reading '3iM76qwej9Tf9ttHcbQp2z') — a GUID used as a key on an undefined object.

Not fatal — the existing fallback recovered and TM opened normally with 63,416 ops. But the handler wraps the whole async activate body (cache read, _materializeNativeSchedule, injectGantt, loadOps, cachePut) and logs only e.message, so nothing identifies which threw.

Logs the first 4 stack frames plus a pre/post-loadOps phase marker. Diagnostic only, no behaviour change.

sw.js v1003 → v1006 (v1004=#1316, v1005=#1317).

🤖 Generated with Claude Code

…nnot locate it

Live user report on Hospital: "§GANTT_CACHE_ERR Cannot read properties of
undefined (reading '3iM76qwej9Tf9ttHcbQp2z')" — a GUID used as a key on an
undefined object. Recovered by the existing fallback (TM opened normally,
63,416 ops) so it is not fatal, but the handler wraps the WHOLE async activate
body — cache read, _materializeNativeSchedule, injectGantt, loadOps, cachePut —
and logs only e.message, so nothing says which of them threw.

Logs the first 4 stack frames plus a pre/post-loadOps phase marker. Diagnostic
only; no behaviour change.

sw.js CACHE_VERSION v1003 -> v1006 (v1004=#1316, v1005=#1317).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@red1oon
red1oon enabled auto-merge (squash) August 12, 2026 08:32
red1oon added a commit that referenced this pull request Aug 12, 2026
…006)

Both are still OPEN and each claims a version this branch would have collided
with. Taking the higher number now avoids the sw.js conflict entirely rather
than resolving one later.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GdPyHB9SRqs5Z6rCRdV7eV
github-actions Bot pushed a commit that referenced this pull request Aug 12, 2026
…ash orphaned (#1320)

#1319 was squash-merged while a follow-up commit was still in flight, so the
version landed as v1005 — the exact orphaning CLAUDE.md warns about. That leaves
main sharing a version with the still-OPEN #1317, so #1317's merge would ship
new schedule JS behind a cache key users already hold. v1007 clears both #1317
(v1005) and #1318 (v1006).


Claude-Session: https://claude.ai/code/session_01GdPyHB9SRqs5Z6rCRdV7eV

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
@red1oon
red1oon merged commit a490d7b into main Sep 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant