fix: handle incoming access_token message from client #194
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kiwicopple
approved these changes
Nov 20, 2021
|
🎉 This PR is included in version 0.17.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
w3b6x9
pushed a commit
that referenced
this pull request
Nov 4, 2022
Stop Postgres extension when a tenant is removed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
access_tokenmessages are not handled by channel processes.What is the new behavior?
access_tokenmessages are handled by channel processes until Realtime security (WALRUS) is shipped.Additional context
Related PR: supabase/realtime-js#116