streaming error about twarc

[flinches]

Is it this?

Blank lines
On slow streams, some messages may be blank lines which serve as “keep-alive” signals to prevent clients and other network infrastructure from assuming the stream has stalled and closing the connection.

[edsu]

Yes, exactly. It would be useful for twarc not to log these that way right? They won't get written to the data output incidentally.

[edsu]

Also, I'm kind of curious to hear how you are using twarc in school, since I work in a university setting where we've been thinking about instructional uses of twitter data collection.

[edsu]

I'm just pushed this up to PyPI too as v0.3.2 if you have installed twarc via pip. Let me know if you notice any problems!

[flinches]

Thanks. It seems to be ok now. And I use it in school for some research group. They gave me project to streaming data from Twitter for many keywords, saving them to files and then next working with it.

[edsu]

Excellent, that's just the use case it was created for. If you go looking for an app to manage data collection like this you might be interested in https://github.com/gwu-libraries/social-feed-manager which manages stuff for you, and pretty much lets the researchers decide what to collect.

[flinches]

Oh thanks. I will look at it and consider usage.

[flinches]

Hello,

can I ask you one question? I have another problem, but i don't know if it is mine or yours. I am getting error 406: Not Acceptable. First time I got it after cca 66 hours and second time it was after cca 86 hours of streaming. I am still using Twarc as library and cannot find anything what could help me. Everything worked well but after that time there was error and then it was just repeating this error. Do you know where could be a problem?

Thanks a lot.

Filip Hadac

[edsu]

Interesting, did you can get any kind of stack trace to indicate where the error was happening? It looks like the Search API can return a 406 if the format is invalid? We've been noticing spurious 404 errors from Twtiter over in #75. Maybe this is similar/related?

[flinches]

I cannot get stack trace now, because I already quit application and run it again, because I am already using it to stream data what we need. Also it is not easy to debug it for me because it is running on server and error is often after 3 days. But i will implement some stack trace to script for next run and will see.

[edsu]

If you run it in a screen session you should be able to reconnect after a few days and see the stack trace. If you want I can update the catch-404 branch to also catch 406, and see if that helps you?

[flinches]

It is ok. I will try it once more and if it fails again, I will let you know and then you can update it. But thanks.