pycurl.error: (18, 'transfer closed with outstanding read data remaining')
Bug #73948 reported by
Wouter van Heyst
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Critical
|
Vincent Ladeuil |
Bug Description
I'm not entirely certain yet where the problem lies, I started getting this error after submitting to pqm "Better connection sharing for pycurl" (http://
So, this could be a problem exposed by that bundle, and/or result from me trying to pull when pqm was processing a merge request (and then some window within that, if it would fail everytime there was a merge going on we could never pull).
I'm attaching the bzr.log of when I was doing a pull in bzr.0.12, will try to determine if a difference is made between using bzr.dev and bzr-0.12 doing the pull. Also pycurl vs urllib is worth a shot.
Changed in bzr: | |
status: | Confirmed → In Progress |
Changed in bzr: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Some more toying around, and it has nothing to do with PQM.
Doing //code. aaronbentley. com/bzr/ bzrrepo/ nested- trees/
bzr pull -v http+pycurl:
fails, whilst
bzr pull -v http+urllib: //code. aaronbentley. com/bzr/ bzrrepo/ nested- trees/
succeeds with current bzr.dev. vila can also reproduce it and is looking into it.
Branches that have no new revisions will not trip you up.