[darcs-devel] [issue1207] pull waits, trying to talk to each server in _darcs/prefs/repos and _darcs/prefs/sources

[Zooko]

New submission from Zooko <zooko at zooko.com>:

This was originally reported in issue1153, but it is obscured by a handful of
other issues.  This bug report is to draw attention to this specific issue:

If you have a server in your _darcs/prefs/sources which does not respond to ssh
connections, darcs will block for something on the order of 60 seconds.  Here's
how to reproduce this problem:

1.  Do a "darcs pull -a $REMOTE_REPO" which pulls a few patches and see how long
it takes.
2.  Do "darcs oblit --all --last=$X" to remove a few patches so that we can
benchmark how long it takes to repull them.
3.  rm _darcs/prefs/repos
4.  rm _darcs/prefs/sources
5.  /bin/rm -rf ~/.darcs/cache
6.  echo "nobody at 192.168.3.2:nodir" > _darcs/prefs/repos
7.  Do the same "darcs pull -a $REMOTE_REPO" that you did earlier.  The bug is
that it takes many minutes -- something 60 seconds for every patch that it pulls.

Hmmmm.  Now I can't reproduce this bug.  :-(

I'm sure that I had this bug reliably before, and I'm sure that I saw it last
week when I was travelling at a security conference.  In both cases, the
solution is to clear out _darcs/prefs/repos and _darcs/prefs/source so that
servers which are currently unreachable are not tried.

There are detailed logs showing this bug happening over on issue1153.  See for
example "out2.txt" in which darcs pauses for long periods of time trying to
connect to the non-existent 192.168.1.147 address.

I wonder why I can't reproduce it?  Argh.

----------
messages: 6610
nosy: dagit, dmitry.kurochkin, kowey, simon, thorkilnaur, zooko
priority: bug
status: unread
title: pull waits, trying to talk to each server in _darcs/prefs/repos and _darcs/prefs/sources

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue1207>
__________________________________