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.

Sign up for GitHub

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

Jump to bottom

LISTEN / NOTIFY appears to be broken after March 26th #332

Open
2 tasks done
Dkendal opened this issue Apr 1, 2024 · 0 comments
Open
2 tasks done

LISTEN / NOTIFY appears to be broken after March 26th #332

Dkendal opened this issue Apr 1, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Dkendal
Copy link

Dkendal commented Apr 1, 2024 •
edited
Loading

Bug report

LISTEN / NOTIFY appears to be broken after March 26th

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

We have an Elixir application that uses Oban for job processing that connects to a supabase postgresql instance via transaction pooling.

Oban makes extensive use of LISTEN/NOTIFY, which has been working without issue for 2 months.

As of March 26th all most listen/notify requests started to fail.

image
@Dkendal Dkendal added the bug Something isn't working label Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Dkendal