These are chat archives for praw-dev/praw

24th
Mar 2017
Bryce Boe
@bboe
Mar 24 2017 04:19
@smoothlystable awesome. I'll give that a try to see if the error is reproducible. Out of curiosity approximately where are you geographically located? I wonder if it's a latency issue affecting the timing.
Bryce Boe
@bboe
Mar 24 2017 05:07
@leviroth actually it seems like it's going through both versions fine, but coveralls isn't merging the responses correctly.
Maybe there's an updated version.
Bryce Boe
@bboe
Mar 24 2017 05:22
Merged your changes despite coveralls's issue.
Thanks!
smoothlystable
@smoothlystable
Mar 24 2017 06:23
@bboe I'm located in Sweden. I'll try on another machine in a different location (but still in Sweden), to see if I get the same result there and if they fail at the same time or something similar.
Bryce Boe
@bboe
Mar 24 2017 14:47
Cool. I'm getting a different consistent error when I run on AWS so I'll probably look into fixing both in prawcore.
I'm guessing the latency from Sweden is what's resulting in praw thinking your session is still valid, but by the time it actually reaches Reddit's server it is no longer valid.
Nevertheless, PRAW (prawcore in this case) should automatically retry said requests which should trigger a token refresh. I should be able to emulate that by externally revoking the access token.
smoothlystable
@smoothlystable
Mar 24 2017 19:12
That make sense. Thanks for checking it out. Seems like it is something network related. I tried the same script on another desktop (other location in Sweden) and it's been running for 13h now, without any errors.