Description
I am running both the WebClient and the RTMClient within a Django 2.2 framework. The WebClient has always worked great for us, but we need the RTM client in certain environments due to firewall issues. Django 2.2 is not really async friendly, so we need to run with run_async=False for now.
With the 2.5 client, I got it to work for the most part, but I would occasionally see the concurrent.futures._base.TimeoutError. Seeing the updates to 2.6, I decided to give it a go.
It works good as long as the messages don't arrive too fast. Anything on the order of like 2 msgs/sec though and the second message is a no-show.
For now I've reverted to the 2.5 client.
Not being totally sure what the expected functionality is, I opened this as a "question". But if y'all feel it's bug-worthy, feel free to set accordingly.
What type of issue is this? (place an x in one of the [ ])
Requirements (place an x in each of the [ ])
Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
slackclient version: 2.6.0
python version: 3.6.9
OS version(s): MacOS, Ubuntu 16.04
Steps to reproduce:
- install new slack_client 2.6.0,
- Use RTM Client with run_async=False
- Not sure it matters, but I am running the client in a separate thread.
- send 2 messages in rapid succession
Expected result:
both messages arrive in fcn decorated by '@RTMClient.run_on(event="message")'
Actual result:
Only first message arrives.
Attachments:
Description
I am running both the WebClient and the RTMClient within a Django 2.2 framework. The WebClient has always worked great for us, but we need the RTM client in certain environments due to firewall issues. Django 2.2 is not really async friendly, so we need to run with run_async=False for now.
With the 2.5 client, I got it to work for the most part, but I would occasionally see the concurrent.futures._base.TimeoutError. Seeing the updates to 2.6, I decided to give it a go.
It works good as long as the messages don't arrive too fast. Anything on the order of like 2 msgs/sec though and the second message is a no-show.
For now I've reverted to the 2.5 client.
Not being totally sure what the expected functionality is, I opened this as a "question". But if y'all feel it's bug-worthy, feel free to set accordingly.
What type of issue is this? (place an
xin one of the[ ])Requirements (place an
xin each of the[ ])Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
slackclient version: 2.6.0
python version: 3.6.9
OS version(s): MacOS, Ubuntu 16.04
Steps to reproduce:
Expected result:
both messages arrive in fcn decorated by '@RTMClient.run_on(event="message")'
Actual result:
Only first message arrives.
Attachments: