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
Describe the bug
The bug occurs when you create a pusher instance that is not in cluster us2. My cluster created was in us3 and I wasn't receiving the channel messages. I narrowed it down to this line here which explicitly sets the cluster to us2. I think this should be using the environment variable set in the application.
I'm happy to keep digging in, but am not sure if this is intentional or not. Am I misinterpreting something?
To Reproduce
Create a pusher Channel's instance that is not in us2.
Try to use chat
The text was updated successfully, but these errors were encountered:
Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.
Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.
To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.
To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss. The OSS Community Manager or the engineers on OSS rotation will follow up.
For full info on how to contribute, please check out our contributors guide.
Describe the bug
The bug occurs when you create a pusher instance that is not in cluster
us2
. My cluster created was inus3
and I wasn't receiving the channel messages. I narrowed it down to this line here which explicitly sets the cluster tous2
. I think this should be using the environment variable set in the application.I'm happy to keep digging in, but am not sure if this is intentional or not. Am I misinterpreting something?
To Reproduce
us2
.The text was updated successfully, but these errors were encountered: