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

fix(realtime): lost postgres_changes on resubscribe #585

Merged
merged 7 commits into from
Nov 5, 2024

Conversation

grdsdev
Copy link
Collaborator

@grdsdev grdsdev commented Oct 30, 2024

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

When rejoining a channel it currently doesn't push the registered postgres_changes.

What is the new behavior?

Push postgres_changes when rejoining.

Additional context

Add any other context or screenshots.

@grdsdev grdsdev requested a review from dshukertjr October 30, 2024 14:11
@grdsdev grdsdev changed the title fix(realtime): losing postgres_changes on resubscribe fix(realtime): losing postgres_changes on resubscribe Oct 30, 2024
@grdsdev grdsdev changed the title fix(realtime): losing postgres_changes on resubscribe fix(realtime): loosing postgres_changes on resubscribe Oct 30, 2024
@grdsdev grdsdev changed the title fix(realtime): loosing postgres_changes on resubscribe fix(realtime): lost postgres_changes on resubscribe Oct 30, 2024
@grdsdev grdsdev force-pushed the fix/realtime-connection-loss branch 2 times, most recently from 2ae98b1 to f6e9d7f Compare October 30, 2024 14:24
@grdsdev grdsdev force-pushed the fix/realtime-connection-loss branch from b26d648 to 6767118 Compare November 4, 2024 19:11
@grdsdev grdsdev merged commit fabc07d into main Nov 5, 2024
23 checks passed
@grdsdev grdsdev deleted the fix/realtime-connection-loss branch November 5, 2024 01:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants