Timeout was reached error with incorrect status: SUCCESS

[tonyxiao]

Bug report

1. Run supabase/postgres docker
2. Run sql

CREATE EXTENSION IF NOT EXISTS pg_net;
select
    net.http_post(
        url:='https://httpbin.org/post',
        body:='{"hello": "world"}'::jsonb
    );

select
  *
from
  net.http_collect_response(1);

@see

pg_net: Timeout was reached - Watch Video

Notice how the status says SUCCESS, but upon inspecting the net._http_response table, it says timeout was reached. Additionally it appears that the request was never made according to the remote server.

[steve-chavez]

Thanks for the report. Note that there's a timeout(by default 2 seconds) you can add to the function.

select
    net.http_post(
        url:='https://httpbin.org/post',
        body:='{"hello": "world"}'::jsonb,
        timeout_milliseconds := 5000
    );

The SUCCESS is indeed a mistake.

[tonyxiao]

I see. What's the default timeout on supabase itself? Or is it simply faster on supabase and therefore within the 2000ms timeframe?

[steve-chavez]

Default it's the same - 2 seconds.

Or is it simply faster on supabase and therefore within the 2000ms timeframe?

Yeah, latency might be lower due to network proximity.

[steve-chavez]

http_collect_response was made a private function on #81.

For now it's better to inspect net._http_response directly. We're going to improve this on #62.