ZGaetano b27b9f6909 fix(s3): keep-alive agents + long timeouts to end socket starvation ... Root cause of stuck 'processing', failed deletes, and dead playback: The mam-api proxies media (/video, /hls pipe the full S3 body through Express), holding long-lived streaming sockets. With the SDK's default http agents (no keep-alive, unbounded but unpooled) those streams starved control-plane calls — DeleteObject and the proxy worker's master download — which timed out (10s connectionTimeout) in bursts. Fixes: - mam-api S3 client: dedicated keep-alive http/https Agents (maxSockets 256) + requestTimeout raised 30s→300s so large master GETs finish. - worker S3 client: previously had NO handler config at all (SDK defaults). Added keep-alive agents + 600s requestTimeout so proxy/conform master downloads (hundreds of MB) don't stall and leave assets in 'processing'.		2026-06-04 12:53:28 +00:00
..
db	add services/worker/src/db/client.js	2026-04-07 21:58:20 -04:00
edl	add services/worker/src/edl/parser.js	2026-04-07 21:58:20 -04:00
ffmpeg	fix(worker): conform — preserve audio + map ProRes/DNxHR codecs	2026-05-28 14:32:49 -04:00
s3	fix(s3): keep-alive agents + long timeouts to end socket starvation	2026-06-04 12:53:28 +00:00
workers	feat(promotion): implement manual growing files promotion via BullMQ queue + pending_migration status + right click Move to S3	2026-06-03 00:38:50 +00:00
index.js	feat(promotion): implement manual growing files promotion via BullMQ queue + pending_migration status + right click Move to S3	2026-06-03 00:38:50 +00:00