[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1299519 - /subversion/trunk/tools/server-side/svnpubsub/svnpubsub/client.py

From: Joe Schaefer <joe_schaefer_at_yahoo.com>
Date: Sun, 11 Mar 2012 20:50:37 -0700 (PDT)

If you go thru the logs on minotaur (and they are the same
for eos eg grep stale --context 10) you will see the connect()
is throwing an (unknown) exception causing the daemon to shut

What I think is behind this is that every so often the FreeBSD
nic drivers stall for up to a minute before resetting themselves.
Sometimes a simple connect will work, other times it takes a few
more tries.

Feel free to adjust the logic to taste, I have nothing but little
patience for the mass of Exception classes to deal with coming

from perl where everything is a string.

> From: Greg Stein <gstein_at_gmail.com>
>To: dev_at_subversion.apache.org; Joe Schaefer <joe_schaefer_at_yahoo.com>
>Sent: Sunday, March 11, 2012 11:44 PM
>Subject: Re: svn commit: r1299519 - /subversion/trunk/tools/server-side/svnpubsub/svnpubsub/client.py
>What did you observe here, and do you have some logs that demonstrate the problem? I tested the reconnect logic, and it all appeared to work, so maybe something else is going on here. The code below blocks the network processing.
>The event should also be a simple word, so the callback can switch on it. In this case, it can call logging.exception() so we can see what was caught. Bare "except:" clauses are always dangerous since it could paper over even a simple typo on an attribute access.
>On Mar 11, 2012 10:03 PM, <joes_at_apache.org> wrote:
Received on 2012-03-12 04:51:21 CET

This is an archived mail posted to the Subversion Dev mailing list.