Merge dev → main: per-post stdout diagnostics + post-field write DRY (#842/#753) #106
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two commits since last main:
eb811e1— per-post handling in the run stdout. Native ingester writes a per-post line (post <id> [<post_type>] body: N chars,— EMPTYwhen 0) into the run stdout — shown in the existing "Raw stdout" panel, parity with gallery-dl's per-file output. DRY:write_post_recordreturns aPostRecordOutcome(downloader owns the read, mirroringdownload_post → MediaOutcome);ingest_coreonly formats. Reverted the earlier bespoke structured panel.0d51b93— single_apply_post_fieldspredicate._apply_sidecarandupsert_post_recordhad verbatim-duplicate post-field writes; consolidated into one helper both call so the two ingest paths can't diverge (#753). Groundwork for milestone #67 (post-first ingest model).No migrations. CI green on dev head
0d51b93(run 1112).After merge: re-pull
:latest, re-run Recapture on StickySpoodge, open the event → Raw stdout → the 9 empties read[<post_type>] body: 0 chars — EMPTY.