You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2024. It is now read-only.
I declared the time collecting tweets to be a week long (604800 seconds) but it stopped after only a few hours.
Expected behavior
I expected it to stop collecting Tweets after a week. To check how long it was running again I have just re-ran it (but this time to check on 4 hours) which resulted in the programme stopping after in less than an hour (see below)
It could be caused on Twitter's end, but it may also be related to the status checks that Twitter sends back. @IsobelleClarke can you share your sessionInfo()?
@IsobelleClarke, I wonder if you managed to resolve this problem? I am experiencing it as well. The slight wrinkle, in my case, is that the stream seems to stop or hang up (as far as I can tell), e.g. something like, Downloading: 19 MB gets stuck in the console and the expected JSON file is much smaller than anticipated.
The problem (I think) actually ended up being the result of the computer needing to restart and update. I think it was the pop-up message that was causing the programme stop running. After restarting and updating the computer it collected with no interruptions, although I am yet to check the size of file and the tweets in their for the dates. However, I checked a couple of hours before it was due to stop and it was still collecting so that seems good to me. Perhaps @rayms you could try restarting. Otherwise, I'm not really sure, have you set the timeout right? Maybe post your code here and @mkearney can help.
Problem
I declared the time collecting tweets to be a week long (604800 seconds) but it stopped after only a few hours.
Expected behavior
I expected it to stop collecting Tweets after a week. To check how long it was running again I have just re-ran it (but this time to check on 4 hours) which resulted in the programme stopping after in less than an hour (see below)
Reproduce the problem
The text was updated successfully, but these errors were encountered: