Skip to content
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

Stream hanging after prolonged uptime #78

Open
FOG-Yamato opened this issue Jun 1, 2023 · 0 comments
Open

Stream hanging after prolonged uptime #78

FOG-Yamato opened this issue Jun 1, 2023 · 0 comments

Comments

@FOG-Yamato
Copy link

The streaming endpoint connection hangs open after a substantial amount of time (between 4 to 50 hours). This can be verified by having a tweet that passes the filters be posted and the data not being received by this connection.

Expected behavior

Stream would close or end when heartbeats no longer are coming from the Twitter API.

Actual behavior

The stream hangs with no data coming through, even possible disconnects sent by the API.

Steps to reproduce the behavior

Open a stream connection and let it work for a couple of hours or days, then verify that the connection is alive by sending a tweet that matches the filter rules.

Ideally the internal stream method would use the newlines as heartbeats to detect if they haven't been received for a period of time and closing down the stream which is not accessible to external code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant