The kit's value conversion converts BigQuery temporal types via Timestamp.fromDate(new Date(value)), but a real TIME value (BigQuery.time("10:30:00").value === "10:30:00") makes new Date("10:30:00") invalid and Timestamp.fromDate throws Value for argument "seconds" is not a valid integer. - so a scheduled query whose results include a TIME column crashes the run. Probe-verified during review of #3056 (IzaakGough); that PR pins the throwing behavior with a test so this fix flips it deliberately. Decide the correct representation (probably keep the raw string, matching what the extension stored). Ledger: #2974.
The kit's value conversion converts BigQuery temporal types via
Timestamp.fromDate(new Date(value)), but a realTIMEvalue (BigQuery.time("10:30:00").value === "10:30:00") makesnew Date("10:30:00")invalid andTimestamp.fromDatethrowsValue for argument "seconds" is not a valid integer.- so a scheduled query whose results include a TIME column crashes the run. Probe-verified during review of #3056 (IzaakGough); that PR pins the throwing behavior with a test so this fix flips it deliberately. Decide the correct representation (probably keep the raw string, matching what the extension stored). Ledger: #2974.