Closed RedChops closed 3 months ago
Have you tested the alternative you described and its working? I'm asking because looking at the edge functions limits the CPU time is 2 seconds which is less than the default 5 seconds. https://supabase.com/docs/guides/functions/limits#runtime-limits
@silentworks I have, I've implemented this alternative in several scripts at this point. The CPU timeout is 2 seconds, yeah, but the total request timeout (according to the next line) is 150 seconds.
A lot of our edge functions themselves make network requests (main reason why we use them over plpgsql stored procedures really), so can take upwards of 30 seconds sometimes, depending.
@RedChops thanks for getting back to me on this. I have added it to the Todo list and will try and get it added.
Feature request
Is your feature request related to a problem? Please describe.
When calling an Edge Function using
client.functions.invoke()
, if the function takes longer than 5 seconds to run I'll get aReadTimeout
exceptionDescribe the solution you'd like
I would like a way to configure the HTTPX timeout for Edge Function calls, the same way we can currently configure PostgREST and Storage. Or a way to supply a custom HTTPX client to supafunc-py
Describe alternatives you've considered
The following will let me create a client with a longer timeout, but it's accessing private interfaces: