Proxy worker: failed jobs for odd-dimension images and truncated ProRes captures #13

New issue

Closed

opened 2026-05-22 22:39:07 -04:00 by zgaetano · 0 comments

zgaetano commented

2026-05-22 22:39:07 -04:00

Owner

Resolved (SVG side) in commit 508e978.

The original IMAGE_CODECS set in services/worker/src/workers/proxy.js covered raster formats (png, mjpeg, jpeg, webp, gif, tiff, bmp, jpegls) but not svg. An uploaded SVG was correctly tagged media_type='image' in the DB, but ffprobe reported codec svg, which fell through to the video branch, found durationMs===null, and died with Empty or truncated source: codec=svg, resolution=0x0.

Two changes:

Added 'svg' to IMAGE_CODECS.
Defensively short-circuit to the poster path when the asset row's media_type === 'image', even if ffprobe returns an unknown codec name (so AVIF/HEIF/JPEG-XL will Just Work in future).

Truncated-ProRes side: the existing 4-KB lower-bound check + the new clear-error wording (Source is empty or truncated (N bytes)…) is what's exposed to the operator now. Bigger structural fixes for odd-dimension videos and ProRes prober quirks aren't in scope here; if those show up again, please file a fresh issue with the specific input.

Closing.

Resolved (SVG side) in commit 508e978. The original IMAGE_CODECS set in `services/worker/src/workers/proxy.js` covered raster formats (`png`, `mjpeg`, `jpeg`, `webp`, `gif`, `tiff`, `bmp`, `jpegls`) but not `svg`. An uploaded SVG was correctly tagged `media_type='image'` in the DB, but ffprobe reported codec `svg`, which fell through to the video branch, found `durationMs===null`, and died with `Empty or truncated source: codec=svg, resolution=0x0`. Two changes: 1. Added `'svg'` to IMAGE_CODECS. 2. Defensively short-circuit to the poster path when the asset row's `media_type === 'image'`, even if ffprobe returns an unknown codec name (so AVIF/HEIF/JPEG-XL will Just Work in future). Truncated-ProRes side: the existing 4-KB lower-bound check + the new clear-error wording (`Source is empty or truncated (N bytes)…`) is what's exposed to the operator now. Bigger structural fixes for odd-dimension videos and ProRes prober quirks aren't in scope here; if those show up again, please file a fresh issue with the specific input. Closing.