Skip to content
This repository was archived by the owner on Aug 21, 2025. It is now read-only.

Conversation

@sidtuladhar
Copy link
Contributor

@sidtuladhar sidtuladhar commented Jan 21, 2025

What kind of change does this PR introduce?

I think it should fix #258

What is the current behavior?

When auto_reconnect is True, the channel is attempted to joined but it uses defaul payload which is empty. Instead it should use the existing payload that was originally used when the channel was first joined.

@sidtuladhar sidtuladhar reopened this Jan 22, 2025
@sidtuladhar sidtuladhar changed the title fix: add token authentication on reconnect fix: send correct payload to channel on reconnect Jan 22, 2025
@juancarlospaco
Copy link
Contributor

LGTM

@coveralls
Copy link

coveralls commented Jan 22, 2025

Pull Request Test Coverage Report for Build 12917870865

Details

  • 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.4%) to 80.91%

Changes Missing Coverage Covered Lines Changed/Added Lines %
realtime/_async/client.py 0 1 0.0%
Totals Coverage Status
Change from base Build 12917512856: 0.4%
Covered Lines: 818
Relevant Lines: 1011

💛 - Coveralls

@silentworks silentworks merged commit 66db32e into supabase:main Jan 22, 2025
7 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Auto-Reconnect is broken when reconnect is triggered by _listen

5 participants