-
Notifications
You must be signed in to change notification settings - Fork 61
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
[Filitered Stream] Stream freezes periodically. #166
Comments
@g8rswimmer Could you check this out? |
@Clashkid155 Have you run with the latest release? I am wondering if the stream fix in the v2.1.5 release may have fixed this. |
@g8rswimmer v2.1.5 doesn't fix it. I attached images of a recent tweet and bot log. As you can see, the bot hasn't been active for 2 days, with no error whatsoever. I think the stream is being killed, but never restarts. |
Just noticed something else, i can start another stream even when one is already running, this shouldn't happen since i don't have higher privilege (academic i think) |
@Clashkid155 |
That's where the whole issue is, the caller doesn't know when it's been killed. |
Did you use this channel for disconnection errors |
I haven't tried that, but don't you think the Btw, Wasn't that introduced recently? |
@Clashkid155 I ran this example It ran for about 25 hours but I did get the disconnect message here I know that you are using the filter stream and I was wondering two things
|
I think I've seen my error (no default in my select). |
@g8rswimmer Seems the whole issue was a user error sorry for wasting your time. |
Having |
I noticed that. |
I noticed an annoying issue with streams where everything freezes with no error.
My code is the same as what's in #158.
The only log I can provide
Each time this happens I've to reboot my service (systemd) which you can tell from the log.
So is there a way to keep checking if the stream is alive? I hope you can imagine how difficult it is to have this problem.
The text was updated successfully, but these errors were encountered: