launchpad plugin gives traceback on XML-RPC connection failure (error 10060: operation timed out)

Bug #281986 reported by yarko
2
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Undecided
Unassigned

Bug Description

From Windows XPSP2, bazaar from self-contained installer - happens w/ both bzr 1.6.1 and 1.7.1 (I tried an upgrade first), and with both windows cmd shell, or cygwin bash shell (they both pull the same path / same bzr):

-------------------------------------------

/cygdrive/d/Workspace
$ bzr branch lp:ipython
bzr: ERROR: socket.error: (10060, 'Operation timed out')

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 857, in run_bzr_catch_errors
  File "bzrlib\commands.pyo", line 797, in run_bzr
  File "bzrlib\commands.pyo", line 499, in run_argv_aliases
  File "bzrlib\builtins.pyo", line 853, in run
  File "bzrlib\bzrdir.pyo", line 894, in open_tree_or_branch
  File "bzrlib\bzrdir.pyo", line 771, in open
  File "bzrlib\lazy_import.pyo", line 125, in __call__
  File "bzrlib\transport\__init__.pyo", line 1527, in get_transport
  File "bzrlib\directory_service.pyo", line 53, in dereference
  File "D:/Program Files/Bazaar/plugins\launchpad\lp_directory.py", line 60, in
look_up
  File "D:/Program Files/Bazaar/plugins\launchpad\lp_directory.py", line 76, in
_resolve
  File "D:/Program Files/Bazaar/plugins\launchpad\lp_registration.py", line 182,
 in submit
  File "D:/Program Files/Bazaar/plugins\launchpad\lp_registration.py", line 147,
 in send_request
  File "xmlrpclib.pyo", line 1147, in __call__
  File "xmlrpclib.pyo", line 1437, in __request
  File "xmlrpclib.pyo", line 1183, in request
  File "xmlrpclib.pyo", line 1297, in send_content
  File "httplib.pyo", line 860, in endheaders
  File "httplib.pyo", line 732, in _send_output
  File "httplib.pyo", line 699, in send
  File "httplib.pyo", line 1134, in connect
  File "<string>", line 1, in connect
error: (10060, 'Operation timed out')

bzr 1.7.1 on python 2.5.2 (win32)
arguments: ['d:\\Program Files\\bazaar\\bzr.exe', 'branch', 'lp:ipython']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
  bzrtools D:\Program Files\bazaar\plugins\bzrtools [1.7.0]
  launchpad D:\Program Files\bazaar\plugins\launchpad [unknown]
  qbzr D:\Program Files\bazaar\plugins\qbzr [0.9.4]
  svn D:\Program Files\bazaar\plugins\svn [0.4.13]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.
/cygdrive/d/Workspace
$ which bzr
/cygdrive/d/Program Files/bazaar/bzr

/cygdrive/d/Workspace
$ bzr --version
Bazaar (bzr) 1.7.1
  Python interpreter: d:\Program Files\bazaar\python25.dll 2.5.2
  Python standard library: d:\Program Files\bazaar\lib\library.zip
  bzrlib: d:\Program Files\bazaar\lib\library.zip\bzrlib
  Bazaar configuration: D:\Profiles\cyt007\Application Data\bazaar\2.0
  Bazaar log file: D:\Profiles\cyt007\My Documents\.bzr.log

Copyright 2005, 2006, 2007, 2008 Canonical Ltd.
http://bazaar-vcs.org/

bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.

/cygdrive/d/Workspace
$

------------------------------------------------------
FYI, not trying to reference by "lp:" works, eg:

  D:\Workspace\ipy>bzr branch http://bazaar.launchpad.net/~ipython-dev/ipython/trunk
  Branched 1147 revision(s).

so this really seems just like an issue of how bzr responds to network timeouts.

Regards,
Yarko

yarko (yarkot)
description: updated
Revision history for this message
Andrew Bennetts (spiv) wrote :

Bzr should certainly not give you a traceback for a network timeout. It should report something like:

bzr: ERROR: unable to resolve "lp:ipython": connection failed: operation timed out (10060)

I'm guessing this happens for you because the HTTPS port is blackholed by a firewall in your network.

Changed in bzr:
status: New → Confirmed
Revision history for this message
Vincent Ladeuil (vila) wrote :

This can also be caused by using a proxy.

python xmlrpc library doesn't handle proxies.

Our http client implementations handle them.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.