Richard Odekerken
Richard Odekerken
So that's great! Would it be possible to add the sessionID as an optional command line parameter?
Oops, my apologies! Last time I read the documentation was two months ago...
It would help a lot if there was some way to know if there were any errors during the search or profile request. Now the only indication of something going...
> by checking for whether the last tweet collected was close to 00:00:00 That is a bit too subjective for me. When is a tweet "close" to 00:00:00 ? And...
This feels more like simple rate limiting or capacity management mechanisms.
And how would it be more effective than just rate limiting on its own? This is all just speculation, there is not a single piece of evidence for a ML...
I’m just sharing my thoughts as well.
How about a binary exponential backoff? Every time it fails it doubles the sleep time. if consecutive_errors_count < self.config.Retries_count: ################################# delay = exp(2, consecutive_errors_count) print('sleeping for {} secs'.format(delay)) time.sleep(delay) #################################...
By the way, can we make those errors/warning messages print to stderr instead of stdout? It would make handling errors so much easier.
Yeah, I agree, but I think those are two different features.