no buffer space available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Critical
|
Andrew Bennetts |
Bug Description
on Windows XP, using the 1.6b3 installer.
trying to branch from latest bzr.dev (plus Andrew Bennetts "[MERGE] Remove registrations of defunct HPSS verbs" patch) running on 64bit Ubuntu 8.04.
C:\Documents and Settings\
k.com/stew-
bzr: ERROR: socket.error: (10055, 'No buffer space available')
Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\fetch.pyo", line 110, in __init__
File "bzrlib\fetch.pyo", line 140, in __fetch
File "bzrlib\fetch.pyo", line 166, in _fetch_
File "bzrlib\
File "bzrlib\
File "bzrlib\
lines
File "bzrlib\
_inventory_lines
File "bzrlib\knit.pyo", line 1292, in iter_lines_
File "bzrlib\knit.pyo", line 1438, in _read_records_iter
File "bzrlib\knit.pyo", line 2272, in get_raw_records
File "bzrlib\pack.pyo", line 253, in iter_records
File "bzrlib\pack.pyo", line 294, in _read_format
File "bzrlib\pack.pyo", line 221, in _read_line
File "bzrlib\pack.pyo", line 185, in readline
File "bzrlib\pack.pyo", line 172, in _next
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
error: (10055, 'No buffer space available')
bzr 1.6b3 on python 2.5.2 (win32)
arguments: ['bzr', 'branch', 'bzr://
ed-backup']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
gtk C:\Documents and Settings\
0\plugins\gtk [0.94.0]
launchpad C:\Program Files\Bazaar\
qbzr C:\Documents and Settings\
0\plugins\qbzr [0.9.1]
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
C:\Documents and Settings\
Related branches
Changed in bzr: | |
assignee: | nobody → spiv |
importance: | Undecided → Critical |
milestone: | none → 1.6 |
It looks like ConventionalRes ponseHandler. read_body_ bytes needs to be more careful about reading smaller amounts of data, like the v1 and v2 protocols' read_body_bytes code does.
Or perhaps we should just enforce smaller recvs in the medium.