fix: Parse RFC 3339 timestamps for feed pubDate #6

Merged

w33ble merged 1 commit from fix/feed-pubdate into main

2026-09-06 20:15:12 -06:00

hijynx commented

2026-09-06 20:07:16 -06:00

Collaborator

Summary

feed.PubDate now tries both timestamp shapes: raw SQLite CURRENT_TIMESTAMP text (2006-01-02 15:04:05) and RFC 3339 (RFC3339Nano), normalizing to RFC-1123Z
Added TestPubDate covering both layouts, fractional seconds, and numeric offsets

Why

Every feed item rendered with the same pubDate = render time. The sqlite driver (modernc.org/sqlite) returns DATETIME columns as time.Time, and database/sql renders that as RFC 3339 when scanned into a string — which the old single-layout parse rejected, so every item fell back to time.Now().

Root-cause probe: querying episodes.created_at through the driver yields driver.Value of type time.Time

## Summary - `feed.PubDate` now tries both timestamp shapes: raw SQLite `CURRENT_TIMESTAMP` text (`2006-01-02 15:04:05`) and RFC 3339 (`RFC3339Nano`), normalizing to RFC-1123Z - Added `TestPubDate` covering both layouts, fractional seconds, and numeric offsets ## Why Every feed item rendered with the same pubDate = render time. The sqlite driver (modernc.org/sqlite) returns `DATETIME` columns as `time.Time`, and `database/sql` renders that as RFC 3339 when scanned into a string — which the old single-layout parse rejected, so every item fell back to `time.Now()`. ## Related - Root-cause probe: querying `episodes.created_at` through the driver yields `driver.Value` of type `time.Time`

hijynx added 1 commit

2026-09-06 20:07:16 -06:00

fix: parse RFC 3339 timestamps for feed pubDate

ci / check (pull_request) Successful in 4m13s

Details

a2bcf4fcdd

The sqlite driver returns DATETIME columns as time.Time and database/sql
renders it RFC3339Nano when scanned into a string, which feed.PubDate
could not parse — every item fell back to now. Try both layouts.