search

slackapi / bolt-python

A framework to build Slack apps using Python
https://slack.dev/bolt-python/
MIT License
1.03k stars 237 forks source link

Unexpected EOF while reading bytes #1031

Closed ashutosh-ag-2024 closed 3 months ago

ashutosh-ag-2024 commented 5 months ago

Reproducible in:

The slack_bolt version

slack-bolt==1.18.0 slack_sdk==3.26.2

Python runtime version

Python 2.7.5

OS info

Ubuntu 20.04

Steps to reproduce:

Running a normal slack app which sends message in the form of blocks and receives input on submit button click. Everything runs normally but in logs there is this below warning, what does this signify and can it cause issues ?

2024-02-20 13:18:42:WARNING: Error on \<machine-ip>:9000 ping: Unexpected EOF while reading bytes 2024-02-20 13:18:42:WARNING: Connection was closed, reconnecting. 2024-02-20 13:18:42:WARNING: Error on socket shutdown: [Errno 107] Transport endpoint is not connected

srajiang commented 5 months ago

@ashutosh-ag-2024 - When does this error occur? Does it occur consistently? Does it impact your app functioning?

seratch commented 4 months ago

This warning might be raised by the underlying modules such as Python standard libraries and WebSocket client libraries. If you see the warnings frequently, that may be caused by the network stability and/or some issues with proxy servers.

Enabling debug-level logging might be helpful to know more details, but if there is no issue affecting your end-users and you're observing the warnings in app logs, you can ignore it so far.

github-actions[bot] commented 3 months ago

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

github-actions[bot] commented 3 months ago

As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.