-
Notifications
You must be signed in to change notification settings - Fork 303
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
Unexepected "Conn close because of error end of file reached" in stream #165
Comments
I just tried using the V2 endpoint instead and got the same result - termination after 5 minutes due to EOF. |
There should not be a time limit on the stream connection - it is more likely to be a twurl or Ruby issue. Have you tried accessing the streaming endpoints via any other code? There are v2 Filtered stream samples here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The following command works as expected, but always terminates with an error "end of file reached" after precisely 5 minutes:
The error is:
Since it's always after 5 minutes (as measured with the linux
time
command), it leads me to the obvious conclusion that there is a 5 minute time limit for listening to streams. Is that the case? I can't find anything in the API docs mentioning this.What is the best way to handle this? Should I just keep re-running the command in a loop?
Expected behavior
The command should run indefinitely unless terminated.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: