; Little-Net-8818:xxx minfrin$ svn update
> > Updating '.':
> > svn: E170013: Unable to connect to a repository at URL '
> https://xxx/trunk'
> > svn: E120171: Error running context: An error occurred during SSL
> communication
> >
> > What mech
On 2025/04/29 08:29:59 Andreas Stieger wrote:
>
> On 2025-04-29 10:00, Michael Osipov wrote:
> > On 2025/04/27 13:00:53 Graham Leggett via dev wrote:
> >
> > What mechanism exists to get the error that occurred during SSL
> > communication?
> >
> > [...]
> > Is there a mechanism to coax an error
On 2025-04-29 10:00, Michael Osipov wrote:
On 2025/04/27 13:00:53 Graham Leggett via dev wrote:
What mechanism exists to get the error that occurred during SSL communication?
[...]
Is there a mechanism to coax an error out of the client side, or is this
something I will have to patch?
Wiresh
t; svn: E170013: Unable to connect to a repository at URL 'https://xxx/trunk'
> svn: E120171: Error running context: An error occurred during SSL
> communication
>
> What mechanism exists to get the error that occurred during SSL communication?
>
> Google is full of people
Hi all,
When attempting a routine svn update from svn 1.14.3 on MacOS (via macports),
I'm getting the following sudden failure:
Little-Net-8818:xxx minfrin$ svn update
Updating '.':
svn: E170013: Unable to connect to a repository at URL 'https://xxx/trunk'
svn: E1201
Ben Reser writes:
> On Sun, Dec 2, 2012 at 9:18 AM, Justin Erenkrantz
> wrote:
>> As for the looping, didn't we put in logic to stop retrying after a number
>> of request failures? That's probably a reasonable thing to do...I
>> definitely think a very nice feature of serf is that it *will* re
:* Subversion Development
*Subject:* Re: Error running context
Hi,
On Sun, Dec 2, 2012 at 3:18 PM, Justin Erenkrantz
wrote:
> On Sun, Dec 2, 2012 at 9:05 AM, Lieven Govaerts wrote:
>>
>> Attached the patch. ( I get paid per mail I send to this list in case
>> no one noticed. ;) )
Hi,
On Sun, Dec 2, 2012 at 3:18 PM, Justin Erenkrantz wrote:
> On Sun, Dec 2, 2012 at 9:05 AM, Lieven Govaerts wrote:
>>
>> Attached the patch. ( I get paid per mail I send to this list in case
>> no one noticed. ;) )
>
>
> The patch looks right to me - the short-circuit to do the simple window
On Sun, Dec 2, 2012 at 3:05 PM, Lieven Govaerts wrote:
> Attached the patch. ( I get paid per mail I send to this list in case
> no one noticed. ;) )
>
> On Sun, Dec 2, 2012 at 2:57 PM, Lieven Govaerts wrote:
> > Hi,
> >
> > On Fri, Nov 30, 2012 at 8:19 PM, Philip Martin
> > wrote:
> >> Stefan
On Sun, Dec 2, 2012 at 9:18 AM, Justin Erenkrantz wrote:
> As for the looping, didn't we put in logic to stop retrying after a number
> of request failures? That's probably a reasonable thing to do...I
> definitely think a very nice feature of serf is that it *will* retry (which
> is helpful in f
On Sun, Dec 2, 2012 at 9:05 AM, Lieven Govaerts wrote:
> Attached the patch. ( I get paid per mail I send to this list in case
> no one noticed. ;) )
The patch looks right to me - the short-circuit to do the simple window can
clearly be called for any window regardless of offset. Perhaps we ca
Attached the patch. ( I get paid per mail I send to this list in case
no one noticed. ;) )
On Sun, Dec 2, 2012 at 2:57 PM, Lieven Govaerts wrote:
> Hi,
>
> On Fri, Nov 30, 2012 at 8:19 PM, Philip Martin
> wrote:
>> Stefan Küng writes:
>>
>>> Here's how to reproduce:
>>>
>>> $ svn co https://tor
On Sun, Dec 2, 2012 at 2:57 PM, Lieven Govaerts wrote:
> Hi,
>
> On Fri, Nov 30, 2012 at 8:19 PM, Philip Martin
> wrote:
>> Stefan Küng writes:
>>
>>> Here's how to reproduce:
>>>
>>> $ svn co https://tortoisesvn.googlecode.com/svn/trunk/src/Resources/tools
>>> tools
>>>
>>> get the file here:
Hi,
On Fri, Nov 30, 2012 at 8:19 PM, Philip Martin
wrote:
> Stefan Küng writes:
>
>> Here's how to reproduce:
>>
>> $ svn co https://tortoisesvn.googlecode.com/svn/trunk/src/Resources/tools
>> tools
>>
>> get the file here:
>> https://skydrive.live.com/redir?resid=D000F60A347E5B37!11352
>> and
Philip Martin writes:
> Philip Martin writes:
>
>> As far as I can tell the problem is the client causing mod_dav_svn to
>> SEGV (serf trunk keep retrying and causing multiple SEGVs). The
>> mod_dav_svn stack trace isn't very useful, I'll need a httpd debug
>> build:
>
> Debug build with pool d
Philip Martin writes:
> As far as I can tell the problem is the client causing mod_dav_svn to
> SEGV (serf trunk keep retrying and causing multiple SEGVs). The
> mod_dav_svn stack trace isn't very useful, I'll need a httpd debug
> build:
Debug build with pool debugging:
Program received signal
Stefan Küng writes:
> Here's how to reproduce:
>
> $ svn co https://tortoisesvn.googlecode.com/svn/trunk/src/Resources/tools
> tools
>
> get the file here:
> https://skydrive.live.com/redir?resid=D000F60A347E5B37!11352
> and replace the one in 'tools' with this one.
I can reproduce locally by i
ion\libsvn_ra_serf\util.c:7
86: (apr_err=20014)
svn: E020014: Error running context: Internal error
Obviously you need commit access to the TSVN repo, so please tell me
your GCode username and I'll get you that.
I've also tried to commit the file to my test repo on a Windows Apache
se
18 matches
Mail list logo
