Hi Linvi,
I appreciate you're a busy man, so thank you very much for taking the time to look into this!
I've been running the program to reproduce the bug with your fix for the past ~20 hrs and it has been running much better than before.
There are still some timeouts, but they may be genuine (Twitter actually timing out).
I'll improve the logging to make sure the timeouts are not consistently for a single user, or anything else which might indicate some sort of problem with TweetInvi rather than Twitter and then get back to you.
One thing I did notice was that TweetinviConfig.CURRENT_WEB_REQUEST_TIMEOUT is still getting ignored by the /1.1/application/rate_limit_status.json requests, which timeout after 10s.
Thanks,
Josh
I appreciate you're a busy man, so thank you very much for taking the time to look into this!
I've been running the program to reproduce the bug with your fix for the past ~20 hrs and it has been running much better than before.
There are still some timeouts, but they may be genuine (Twitter actually timing out).
I'll improve the logging to make sure the timeouts are not consistently for a single user, or anything else which might indicate some sort of problem with TweetInvi rather than Twitter and then get back to you.
One thing I did notice was that TweetinviConfig.CURRENT_WEB_REQUEST_TIMEOUT is still getting ignored by the /1.1/application/rate_limit_status.json requests, which timeout after 10s.
Thanks,
Josh