Skip to content

fix(aggregator): skip invalid Gmail receipt dates without dropping the batch (#2448) - #3439

Merged
dezren39 merged 1 commit into
mainfrom
queue/5335-2448-gmail-date-guard
Nov 1, 2026
Merged

dezren39 merged 1 commit into
mainfrom
queue/5335-2448-gmail-date-guard

Conversation

@dezren39

@dezren39 dezren39 commented Nov 1, 2026 •

Copy link
Copy Markdown
Member

Fixes #2448. Queue task 5335 (follow-up of triage task 3663).

What

In scripts/produce-charge-candidates.ts, the Gmail per-message day was derived as (m.message_sent_at?.user_local ?? "").slice(0, 10) || isoDay(new Date(m.date ?? "")) before the format/skip check — so a message with no local day and a missing/garbled date made isoDay throw RangeError on an invalid Date. The throw escaped gmailCandidates, and main()'s catch discarded the whole Gmail batch (Plaid candidates only) for one bad message.

The derivation now goes through an exported pure helper, gmailMessageDay: the triage local day when present, else the parsed message date, else "" for a missing/garbled date — the existing format check then counts that message as skipped and the loop continues with the rest of the batch. No behavior change for well-formed messages; CLI --start/--end validation is #3333 and untouched, as are Plaid parsing, amount/merchant extraction, and charge matching.

Tests (laptop, Bun)

  • New gmailMessageDay (#2448) describe in test/produce-charge-candidates.test.ts: local day wins; parseable date used; missing date → "" (no throw); garbled/empty date → ""; a bad message in a batch does not stop later messages resolving.
  • bun test test/produce-charge-candidates.test.ts — 20/20 pass (15 pre-existing + 5 new).
  • bun run typecheck — 6 errors, the identical pre-existing set on clean main (verified by stash comparison); none in the touched files.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

@dezren39
dezren39 requested a review from a team as a code owner November 1, 2026 09:05
@coderabbitai

coderabbitai Bot commented Nov 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 40 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 934fb5e4-0021-4445-b7ec-a04fd530c594
Commits

Reviewing files that changed from the base of the PR and between ba2e97d and 151995f.

Files selected for processing: 2
  • pm-stack/aggregator/scripts/produce-charge-candidates.ts
  • pm-stack/aggregator/test/produce-charge-candidates.test.ts
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-01T09:07:02.017772Z 151995f PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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.

aggregator(charges-producer): one Gmail message with a missing/garbled date throws RangeError and discards the whole Gmail candidate batch

1 participant