Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pg_net function hooks stop working after an error #42

Closed
imagitama opened this issue Aug 30, 2021 · 0 comments
Closed

pg_net function hooks stop working after an error #42

imagitama opened this issue Aug 30, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@imagitama
Copy link

Bug report

Describe the bug

Whenever any function related to pg_net fails (eg. this error #38) the extension stops trying to send any request.

It inserts the request into net.http_request_queue but nothing cares after that.

Re-enabling pg_net and recreating my triggers fixes the error.

To Reproduce

  1. Enable pg_net extension
  2. Create a new HTTP trigger sending a request anywhere
  3. Sometimes that error I linked above occurs (cannot confirm - still investigating)
  4. Cause the HTTP trigger to happen (eg. UPDATE)
  5. Nothing happens

Expected behavior

Supabase recovers from the error gracefully instead of exploding and requiring me to re-enable the extension and my triggers.

@w3b6x9 w3b6x9 transferred this issue from supabase/supabase Aug 30, 2021
@steve-chavez steve-chavez added the bug Something isn't working label Sep 14, 2022
steve-chavez added a commit to steve-chavez/pg_net that referenced this issue Sep 15, 2022
steve-chavez added a commit to steve-chavez/pg_net that referenced this issue Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants