3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	4fb6350aa1	Answer 415 for a source whose first bytes do not match its Content-Type (closes #253) ... A body whose first bytes are not those of the format its Content-Type names answered 500 on both image routes, was logged as pixa's own error, and was fetched again on every request. Both routes now answer 415 for each error the first-bytes check returns, and the image service logs the refused source at warning level. The failure also gets a negative cache entry, as an upstream error status does, so the source URL is not fetched again for 5 minutes, and meanwhile an image that would need that fetch answers 502. README.md says so. The case of TestService_Get_ConcurrentMissesShareAFailure that expected such a source to be fetched again now expects the negative cache, as #280 (comment) allows. Model: opus-5-5	2026-10-20 14:40:51 +02:00
clawbot	3ba9ae9c39	Stop a transcode whose request has ended before it encodes (closes #243) ... Process looked at its context only while waiting for a processing slot, so a transcode kept its slot and worked on after its request's downstream_timeout. acquireSlot now gives the slot back when the context has ended by the time it has one, and encode returns the context's error without beginning. govips gives pixa no way to stop libvips once an encode has begun, so that encode keeps its slot. A request waiting on a shared transcode stopped at the first request's deadline is answered 503, not 500. README.md "Routes" says both. Model: opus-5-5	2026-10-15 18:44:11 +02:00
clawbot	697c14633b	Share one fetch and transcode among concurrent misses (closes #65) ... Requests that missed the same variant at once each fetched and transcoded it. They now share one call through golang.org/x/sync/singleflight, keyed on the variant cache key. The first request processes the variant with a context that ignores its cancellation but keeps its deadline; the others wait for its result, holding no connection or processing slot, and return as soon as their own context ends. The processing request waits even then, up to its deadline. Each request counts one miss; the processing counts its fetch and transcode once. A panic while processing is reported through the request's Sentry hub, when there is one, and becomes an error instead of stopping pixad. Model: opus-5-5	2026-10-04 01:58:48 +02:00