Closed Brotakuu closed 6 years ago
Sorry for the inconvenience, this is another artifact from the PRAW3 to PRAW4 transition. The posts used to be collected oldest-first so that's why it only checks for newer posts when you run it a second time. Now they're collected newest-first and that isn't as good.
You can still provide the --upper
and --lower
arguments on the commandline. So for example lower
should be the timestamp that the subreddit was created, which you can find on the json:
https://www.reddit.com/r/askreddit/about.json Search for "created_utc"
For upper
you can use the timestamp from before it crashed. July 14 2015 is approximately 1436897779 but maybe you should set it a bit higher to account for possible timezone offsets.
TLDR:
> timesearch timesearch -r askreddit --upper 1436984179 --lower 1201146735
The cause is just a read timeout, which means the website was probably too busy. Timestamp searching is fairly expensive which is probably one of the reasons they're killing it / the new platform doesn't support it. It's not your fault.
After running timesearch through a huge sub, the bot exited with an exception.
Is there a way to resume progress from where it exited? Running the
timesearch
again only grabs the most recent threads from the top (does not attempt to continue where it left off).Also: any idea what might be the cause? (running 2 instances with different apps configured on mac os)