You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The auto_reconnect feature, which was fixed in PR #203, is not functioning as expected. When the connection to the realtime server is lost and reconnected using auto_reconnect = true, the client successfully rejoins the channel but does not resubscribe to the postgres_changes events.
To Reproduce
An extracted version of the code setup:
client = AsyncRealtimeClient(f"{url}/realtime/v1", key, auto_reconnect=True)
await client.connect()
channel = client.channel("new-test-db-channel")
await channel.on_postgres_changes(
"INSERT",
schema="public",
table="table_masked",
filter="filter_masked",
callback=my_callback_function,
).on_postgres_changes(
"UPDATE",
schema="public",
table="table_masked",
filter="filter_masked",
callback=my_callback_function,
).subscribe()
# before we listen, we are doing some processing
process_something()
await client.listen()
Expected behavior
After the connection is automatically reestablished, all postgres_changes events should be resubscribed.
At 2024-09-30T13:08:13.712427114Z no postgres_changes are sent to the realtime server. On the first connect at 2024-09-30T13:05:21.388617410Z they have been sent.
The INFO: Channel phoenix not found message appears repeatedly (is this related to the heartbeat?). It becomes a bit overwhelming as it floods the logs. I'm connecting to a Supabase cloud instance. Is there any configuration I need to set up to ensure this channel exists?
System information
OS: Linux Alpine 3.19
Version of python: 3.12
Version of realtime-py: 2.0.5
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
The
auto_reconnect
feature, which was fixed in PR #203, is not functioning as expected. When the connection to the realtime server is lost and reconnected usingauto_reconnect = true
, the client successfully rejoins the channel but does not resubscribe to thepostgres_changes
events.To Reproduce
An extracted version of the code setup:
Expected behavior
After the connection is automatically reestablished, all postgres_changes events should be resubscribed.
Log
2024-09-30T13:08:13.712427114Z
nopostgres_changes
are sent to the realtime server. On the first connect at2024-09-30T13:05:21.388617410Z
they have been sent.INFO: Channel phoenix not found
message appears repeatedly (is this related to the heartbeat?). It becomes a bit overwhelming as it floods the logs. I'm connecting to a Supabase cloud instance. Is there any configuration I need to set up to ensure this channel exists?System information
The text was updated successfully, but these errors were encountered: