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
I get this error about 50% of the time. I then have to restart the bot. It's perhaps related to #95, which is the same behavior.
/Users/aaronmeurer/.sympy/sympy-bot.conf
> Using /Users/aaronmeurer/.sympy/sympy-bot.conf
> Checking username and password ...
> OK.
> Working directory: /var/folders/wc/dppcpmxs1tlb36nqcw853wkm0000gn/T/sympy-bot-tmpUikPsd
Traceback (most recent call last):
File "./sympy-bot", line 337, in <module>
main()
File "./sympy-bot", line 130, in main
review(n, options, username, password)
File "./sympy-bot", line 258, in review
pull = github_get_pull_request(config.repository, n)
File "/Users/aaronmeurer/Documents/Python/sympy/sympy-bot/utils.py", line 121, in github_get_pull_request
data = json.load(urlopen(url % n))
File "/sw/lib/python2.7/urllib2.py", line 126, in urlopenreturn _opener.open(url, data, timeout)
File "/sw/lib/python2.7/urllib2.py", line 394, in open
response =self._open(req, data)
File "/sw/lib/python2.7/urllib2.py", line 412, in _open'_open', req)
File "/sw/lib/python2.7/urllib2.py", line 372, in _call_chain
result = func(*args)
File "/sw/lib/python2.7/urllib2.py", line 1199, in http_openreturnself.do_open(httplib.HTTPConnection, req)
File "/sw/lib/python2.7/urllib2.py", line 1174, in do_openraise URLError(err)
urllib2.URLError: <urlopen error [Errno 54] Connection reset by peer>
The text was updated successfully, but these errors were encountered:
This also changes all retries to use a doubled waiting scheme, where it waits
for 1 second, then 2 seconds, then 4 seconds, then 8 seconds, and so on. This
is for example what GMail does. This prevents us from DOSing the server.
The easiest way to test this is to disconnect yourself from the internet and
try to review a pull request.
Closessympy#96.
I get this error about 50% of the time. I then have to restart the bot. It's perhaps related to #95, which is the same behavior.
The text was updated successfully, but these errors were encountered: