pycurl timeout gives traceback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Breezy |
Fix Released
|
Low
|
Jelmer Vernooij |
Bug Description
Bzr proxy server problems.
Doing this bzr pull https:/
Bzr behaves strange with proxies. Usually if proxy is not configured it hangs for about two or more minutes and does not show any activity. It'll be better if bzr will comment what is it doing at the moment.
Traceback:
Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run_
File "/usr/lib/
return self._operation
File "/usr/lib/
self.cleanups, self.func, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
possible_
File "/usr/lib/
_do_directive)
File "/usr/lib/
redirected
File "/usr/lib/
return obj(*args, **kwargs)
File "/usr/lib/
return action(transport)
File "/usr/lib/
return StringIO(
File "/usr/lib/
f = self.get(relpath)
File "/usr/lib/
code, response_file = self._get(relpath, None)
File "/usr/lib/
return self._get_
File "/usr/lib/
self.
File "/usr/lib/
curl.perform()
error: (28, 'connect() timed out!')
Related branches
- Martin Packman: Approve
-
Diff: 991 lines (+20/-691)9 files modifiedbreezy/tests/features.py (+0/-1)
breezy/tests/http_server.py (+0/-22)
breezy/tests/https_server.py (+0/-14)
breezy/tests/test_bzrdir.py (+0/-12)
breezy/tests/test_http.py (+11/-169)
breezy/transport/__init__.py (+4/-18)
breezy/transport/http/__init__.py (+1/-1)
breezy/transport/http/_pycurl.py (+0/-454)
doc/en/release-notes/brz-3.0.txt (+4/-0)
Changed in bzr: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Critical |
importance: | Critical → Low |
milestone: | none → 3.0.0 |
Changed in brz: | |
status: | Triaged → Fix Released |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Your network firewall is apparently just dropping outbound connections that don't go through the proxy, so it's hard for bzr to tell the difference between this and a very slow network.
Still, we could:
1- give a better message rather than a traceback
2- show that we're trying to connect to the host, so that you have a clue why it's blocking