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

Re: libneon/subversion bug

From: Gustavo Niemeyer <niemeyer_at_conectiva.com>
Date: 2002-09-10 00:48:20 CEST

Hi again Joe!

Thanks for your quick answer!

> > I'm not sure if this is a bug in libneon (0.23.3) or subversion (3140),
> > but a command like "svn co https://INEXISTANT/foo /foo/bar" has
> > segfaulted inside libneon.
>
> Thanks for the backtrace - does the patch below fix it? (If so, ra_dav

Yes, it fixes the problem completely.

> must treat a request failure as non-fatal at some point, and carry on
> using the session; this is a legitimate use of the neon API but might
> produce strange behaviour, since failing DNS lookups will be retried on
> each request in the current implementation)

Hummm.. I see. Your patch seems to implement the behavior that is
currently expected by subversion. Look:

[niemeyer_at_matrix neon-0.23.3]$ svn co https://repos/foo/bar /tmp/foo
svn: RA layer request failed
svn: PROPFIND of /: Could not resolve hostname `repos': Host not found

I'm not sure if subversion should treat something like this as
non-fatal, since a host failure is usually something definitive, and
kills any further actions.

Maybe subversion should just detect this error in some other way then?

> (BTW, can you CC suspected neon bugs to neon@webdav.org?)

Oh.. I'm sorry. I should have done this before.

Thank you!

-- 
Gustavo Niemeyer
[ 2AAC 7928 0FBF 0299 5EB5  60E2 2253 B29A 6664 3A0C ]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 10 01:17:09 2002

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