-
Notifications
You must be signed in to change notification settings - Fork 853
Closed as not planned
Labels
auto-triage-stalediscussionM-T: An issue where more input is needed to reach a decisionM-T: An issue where more input is needed to reach a decisionneeds infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more info
Description
Reproducible in:
pip freeze | grep slack
Python 3.12.10
The Slack SDK version
pip freeze | grep slack
Python runtime version
Python 3.12.10
OS info
#225-Ubuntu SMP Fri Jan 10 22:23:35 UTC 2025
Steps to reproduce:
- use the sample from offical site https://tools.slack.dev/python-slack-sdk/socket-mode/
- kill the tcp session(websocket) between bot and slack sever by tcpkill or iptables or something else
- wait for auto reconnection
- after that the bot will receive event notification no more
- a workaround i figure out myself: after this happens, use client.web_client to do something, query a channel history or post a message to a channel, then the event notication works again.
Expected result:
everything goes well after auto re-connection
Actual result:
no more events notification after that
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
auto-triage-stalediscussionM-T: An issue where more input is needed to reach a decisionM-T: An issue where more input is needed to reach a decisionneeds infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more info