You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Prevent invalid month strings from hanging the gap timeline loop #619
GapSearch.prepare() in assets/gaps/search-core.js accepts any ^\d{4}-\d{2} date prefix (including out-of-range months such as 00 or 13–99), while nextMonth(ym) only rolls the year over when m === 12 and summarizeAnalytics() loops with lexicographic cur <= last. If items carry e.g. 2026-13-01 and 2027-01-01, spanMonths is 0 (<= 60) and nextMonth increments '2026-14', ..., '2026-100', ... forever ('2026-...' <= '2027-01'), hanging the Web Worker.
Fix:
Restrict posedMonth, resolvedMonth, and matchesMonth to valid calendar months (01–12).
Drive month gap-filling with bounded integer month arithmetic rather than string cur <= last.
Add unit tests covering invalid month strings, year rollover, empty-month interpolation, and >60-month spans.
Activity
Fix adversarial review findings across gap analyses, UI, build, and QA