pushing to team-shared supermirror sftp bazaar branch fails with IOError

[Wouter van Heyst]

Trying to make use of a team shared branch I tried to push my changes to:

   sftp://bazaar.launchpad.net/~bzrk/bzrk/dev

but that resulted in an error:

sftp://bazaar.launchpad.net/%7Ebzrk/bzrk/dev/
bzr: ERROR: exceptions.IOError: bf
  at /home/larstiq/src/bzr-0.8/bzrlib/transport/sftp.py line 540
  in _translate_io_exception

This happened with bzr.dev, bzr-0.8, local branch as weave and as knit. A log will be attached.

[Wouter van Heyst (larstiq)]

~/.bzr.log from the push attempt

[Andrew Bennetts (spiv)]

Hi Wouter,

It seems it failed to create a "bf" file ("revision-store/bf", maybe?), perhaps due to a permission error (unlikely; if you can see the directory at all that shouldn't be possible), or perhaps due to the directory already existing (also unlikely; that directory certainly doesn't seem to exist!). The server didn't log any abnormal errors at that time.

But I can't reproduce this... perhaps it's already been fixed by accident?

Could you try this again, and let me know how it goes?

Also, I have a change in the works that will greatly improve the error reporting of things like permission errors from the SFTP server (part of the work for bug #33223), if this problem still exists we may get more useful information after that's put into production.

Thanks!

[Robert Collins (lifeless)]

we believe this to be a bug in paramiko that was fixed after 1.5.0 - can you please update your paramiko to 1.5.2 or newer?

if that is the case, then the fault is probably with debians bzr package not requiring a newer paramiko.

[Andrew Bennetts (spiv)]

Discussion about a seperate problem on IRC made me realise this is probably a bug with the way the current code reports "no such file" errors to the SFTP client -- bzr optimistically tries to access directories that might not be there (because it's faster in the common case that they are). Obviously bzr relies on "no such file" errors for that to work, though. The aforementioned Twisted update fixes that, so I'll get that put in to production ASAP, and we'll see if that sorts it out.

[Wouter van Heyst (larstiq)]

On Tue, Jun 13, 2006 at 12:17:33PM -0000, Robert Collins wrote:
> we believe this to be a bug in paramiko that was fixed after 1.5.0 - can
> you please update your paramiko to 1.5.2 or newer?

paramiko 1.5.2 made the problem go away.
>
> if that is the case, then the fault is probably with debians bzr package
> not requiring a newer paramiko.

I used the 0.8 source so that wouldn't have helped me. I agree the
package should require a newer paramiko, which also requires a newer one
actually being in Debian, pinging the maintainers.

Wouter van Heyst

[Andrew Bennetts (spiv)]

The better error reporting from the server (bug 33223) is fixed, and the paramiko bug is also fixed by using a newer paramiko. And there are plenty of team-shared branches working just fine, so it doesn't seem to be a current problem.

I'll close this bug in the next few days, unless someone replies with more information that it is still an issue.

[Wouter van Heyst (larstiq)]

On Fri, Jul 21, 2006 at 08:13:55AM -0000, Andrew Bennetts wrote:
> The better error reporting from the server (bug 33223) is fixed, and the
> paramiko bug is also fixed by using a newer paramiko. And there are
> plenty of team-shared branches working just fine, so it doesn't seem to
> be a current problem.
>
> I'll close this bug in the next few days, unless someone replies with
> more information that it is still an issue.

With the paramiko as in Debian sid it still fails:
    > bzr push sftp://bazaar.launchpad.net/~bzrk/bzrk/dev
    bzr: ERROR: checkout

In 0.8.2 it is slightly nicer without giving the entire backtrace:

bzr: ERROR: exceptions.IOError: checkout
  at /usr/lib/python2.4/site-packages/bzrlib/transport/sftp.py line 540
    in _translate_io_exception

After installing paramiko 1.6.1, it does work.

Wouter van Heyst

[David Allouche (ddaa)]

Since bug 33223 is "fix released", and the remaining misbehaviour appear to due to a bug in paramiko, closing the launchpad-bazaar bug and confirming the bzr bug.

[John A Meinel (jameinel)]

As this is a paramiko bug. Closing the bzr bug, and moving it to paramiko. And then closing the paramiko bug, because it has already been fixed.

[John A Meinel (jameinel)]

Robey, I'm not a member of this group. Feel free to close this bug.

[Robey Pointer (robey)]

sorry, didn't notice this before. :)