You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Paul Burba <pt...@gmail.com> on 2009/05/27 18:11:46 UTC
Issues with serf, scheduled for 1.7.0
Due to some problems with the dev@svn.t.o mailing list, Stefan
Sperling can't create any new threads at the moment, so I'm doing it
for him.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2355876
Re: Issues with serf, scheduled for 1.7.0
Posted by "C. Michael Pilato" <cm...@collab.net>.
Stefan Sperling wrote:
> On Wed, May 27, 2009 at 02:11:46PM -0400, Paul Burba wrote:
>> Due to some problems with the dev@svn.t.o mailing list, Stefan
>> Sperling can't create any new threads at the moment, so I'm doing it
>> for him.
>
> Thanks Paul!
>
> *grabs mic*
>
> Yes, jackr is investigating. For some reason the dev list does
> not want mail from me unless an in-reply-to header pointing
> to the dev list is set... or something... we still don't really know.
>
> So what I wanted to say was this:
>
> Just poking serf people:
>
> There has been talk of making serf the default HTTP backend for 1.7.0.
> It is the default in trunk right now, IIRC.
>
> But there are two blocking issues for serf becoming the default
> in 1.7.0, and nobody seems to be working on them:
>
> #3375: ra_serf desperately needs an error handling overhaul
> http://subversion.tigris.org/issues/show_bug.cgi?id=3375
> (this one might be a bit of work)
>
> #3301: Cannot build without OpenSSL
> http://subversion.tigris.org/issues/show_bug.cgi?id=3301
> (this one should be easy)
You missed the "editor drive ordering problem" issue:
#2932: ra_serf violates editor API constraints of depth-first-ness
http://subversion.tigris.org/issues/show_bug.cgi?id=2932
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2355891
RE: Issues with serf, scheduled for 1.7.0
Posted by Bert Huijben <rh...@sharpsvn.net>.
> -----Original Message-----
> From: Arfrever Frehtes Taifersar Arahesis
> [mailto:Arfrever.FTA@GMail.Com]
> Sent: woensdag 19 augustus 2009 15:05
> To: Stefan Sperling; dev@subversion.tigris.org
> Cc: Paul Burba
> Subject: Re: Issues with serf, scheduled for 1.7.0
>
> 2009-05-27 20:36:26 Stefan Sperling napisał(a):
> > On Wed, May 27, 2009 at 02:11:46PM -0400, Paul Burba wrote:
> > > Due to some problems with the dev@svn.t.o mailing list, Stefan
> > > Sperling can't create any new threads at the moment, so I'm doing
> it
> > > for him.
> >
> > Thanks Paul!
> >
> > *grabs mic*
> >
> > Yes, jackr is investigating. For some reason the dev list does
> > not want mail from me unless an in-reply-to header pointing
> > to the dev list is set... or something... we still don't really know.
> >
> > So what I wanted to say was this:
> >
> > Just poking serf people:
> >
> > There has been talk of making serf the default HTTP backend for
> 1.7.0.
> > It is the default in trunk right now, IIRC.
> >
> > But there are two blocking issues for serf becoming the default
> > in 1.7.0, and nobody seems to be working on them:
> >
> > #3375: ra_serf desperately needs an error handling overhaul
> > http://subversion.tigris.org/issues/show_bug.cgi?id=3375
> > (this one might be a bit of work)
The plumbing noted in this issue is done.
There are still several network triggerable SVN_ERR_ASSERT()/SVN_ERR_MALFUNCTION() calls that should be removed, but returning errors is much easier from most code paths. This work removed at least a dozen error leaks.
> > #3301: Cannot build without OpenSSL
> > http://subversion.tigris.org/issues/show_bug.cgi?id=3301
> > (this one should be easy)
>
> This also must be fixed:
> Serf Issue #28: Serf doesn't work with non HTTP/1.1 proxies
> (squid/perlbal...)
> http://code.google.com/p/serf/issues/detail?id=28
Bert
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2385223
Re: Issues with serf, scheduled for 1.7.0
Posted by Arfrever Frehtes Taifersar Arahesis <Ar...@GMail.Com>.
2009-05-27 20:36:26 Stefan Sperling napisał(a):
> On Wed, May 27, 2009 at 02:11:46PM -0400, Paul Burba wrote:
> > Due to some problems with the dev@svn.t.o mailing list, Stefan
> > Sperling can't create any new threads at the moment, so I'm doing it
> > for him.
>
> Thanks Paul!
>
> *grabs mic*
>
> Yes, jackr is investigating. For some reason the dev list does
> not want mail from me unless an in-reply-to header pointing
> to the dev list is set... or something... we still don't really know.
>
> So what I wanted to say was this:
>
> Just poking serf people:
>
> There has been talk of making serf the default HTTP backend for 1.7.0.
> It is the default in trunk right now, IIRC.
>
> But there are two blocking issues for serf becoming the default
> in 1.7.0, and nobody seems to be working on them:
>
> #3375: ra_serf desperately needs an error handling overhaul
> http://subversion.tigris.org/issues/show_bug.cgi?id=3375
> (this one might be a bit of work)
>
> #3301: Cannot build without OpenSSL
> http://subversion.tigris.org/issues/show_bug.cgi?id=3301
> (this one should be easy)
This also must be fixed:
Serf Issue #28: Serf doesn't work with non HTTP/1.1 proxies (squid/perlbal...)
http://code.google.com/p/serf/issues/detail?id=28
--
Arfrever Frehtes Taifersar Arahesis
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2385210
Re: Issues with serf, scheduled for 1.7.0
Posted by Stefan Sperling <st...@elego.de>.
On Wed, May 27, 2009 at 02:11:46PM -0400, Paul Burba wrote:
> Due to some problems with the dev@svn.t.o mailing list, Stefan
> Sperling can't create any new threads at the moment, so I'm doing it
> for him.
Thanks Paul!
*grabs mic*
Yes, jackr is investigating. For some reason the dev list does
not want mail from me unless an in-reply-to header pointing
to the dev list is set... or something... we still don't really know.
So what I wanted to say was this:
Just poking serf people:
There has been talk of making serf the default HTTP backend for 1.7.0.
It is the default in trunk right now, IIRC.
But there are two blocking issues for serf becoming the default
in 1.7.0, and nobody seems to be working on them:
#3375: ra_serf desperately needs an error handling overhaul
http://subversion.tigris.org/issues/show_bug.cgi?id=3375
(this one might be a bit of work)
#3301: Cannot build without OpenSSL
http://subversion.tigris.org/issues/show_bug.cgi?id=3301
(this one should be easy)
In case these issues aren't fixed, it looks like there will be vetos
for serf to become the default and we might have to flip the default
back to neon before release.
I'm not asking anyone in particular to fix these issues.
I'm just pointing this out so that there is no surprise late in the
game close before 1.7-release when this issue will come up again.
Because *now* is the time to fix bugs!
When we want to release it is too late to fix them, in a rush.
Stefan