New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add exception handling for socket mode - socket.timeout: the read operation timed out #1181
Comments
Hey @tom0010 👋🏻 Thanks for reaching out and cool to hear that you're running 5 socket connections! We've found the Socket Mode connection to timeout/reconnection periodically, which is what you've linked in slackapi/bolt-python#529 I just want to clarify that your question is how to silence the traceback output when a socket times-out? Ideally, being able to handle the exception yourself? |
Hi @mwbrooks thats exactly it, the traceback is informative but actually I don’t need to see the whole trace when a socket connection times out, so I’d like to catch the exception with a log message, saying something like it timed out and a new socket will be started or something. |
Great, thanks @tom0010! I had a chat with @seratch. He pointed out that I'm going to transfer this issue to slackapi/python-slack-sdk and switch it to a feature enhancement! |
…eout: the read operation timed out
I run socket mode with 5 sockets, which works fine, however sometimes I get a timeout, and it gives me a full traceback about socket.timeout.
I'm fine with it right now, as it just opens a new socket connection, however in the logs I'm getting a full traceback.
Are we able to handle this a bit better as it's causing a large amount of logs?
Really I don't care about this, that's why I'd like to just send a message saying it timed out and to continue working, which is why I'd like to handle this better.
This is also related to slackapi/bolt-python#529
Category (place an
x
in each of the[ ]
)Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: