EdgeRuntime.waitUntil cpu time limits for image processing...
One of the use cases that supabase background jobs claim to address in the docs is the "user uploads some image/pdfs and you need to process them - e.g., manipulate them in imageMagick, etc". But unless I am missing something, background tasks really aren't useful for this at all. I've got some simple re-size/optimizations going on with magick-wasm and a batch of 3 or more 4MB+ jpgs start to hit that 2second CPU limit. I naively thought that
EdgeRuntime.waitUntil(resizeUserUploads(...)) would somehow enable the processing pipeline to fully run and avail itself of the 2 second max CPU time in the request handler. But that's not the case -- still hitting the 2 second CPU limit in Background-land. Am I completely missing something here, or do I need to offload the processing to trigger.dev or an aws lambda ..?