Hi Jack,
On Wed, May 20, 2020 at 05:23:08PM +0200, PR Bot wrote:
> Author: Jack Neely
> Number of patches: 1
>
> This is an automated relay of the Github pull request:
>The agent-check fail state is represented as "fail"
>
> Patch title(s):
>The agent-check fail state is represented
вт, 26 мая 2020 г. в 12:02, Willy Tarreau :
> Hi Ilya,
>
> On Sat, May 23, 2020 at 03:47:58PM +0500, ??? wrote:
> > From: Ilya Shipitsin
> > Date: Sat, 23 May 2020 15:35:36 +0500
> > Subject: [PATCH] CLEANUP: src/checks.c: ignore return value using
> DISGUISE(..)
> >
> > we do not want
Hi Bertrand,
On Fri, May 22, 2020 at 05:03:46PM +0100, Bertrand Jacquin wrote:
> spoa server fails to build when python3.8 is not available. If
> python3-config --embed fails, the output of the command is registered in
> check_python_config. However when it's later used to define
>
Hi Joao,
On Thu, May 21, 2020 at 09:41:19PM -0300, Joao Morais wrote:
>
> Hello list, the 401 is one of the http status code haproxy generates itself:
>
> https://github.com/haproxy/haproxy/blob/v2.1.0/doc/configuration.txt#L363
>
> This cannot however be overwritten using the errorfile
Hi Igor,
On Sun, May 24, 2020 at 10:35:10AM +1000, Igor Cicimov wrote:
> Hi guys,
>
> We are getting segfaults with haproxy 1.8.25 and thought I would ask if
> this rings any bell:
>
> segfault at 5609a853 ip 7f1b93928c10 sp 7ffd5e731fd8 error 4 in
>
Hi Ilya,
On Sat, May 23, 2020 at 03:47:58PM +0500, ??? wrote:
> From: Ilya Shipitsin
> Date: Sat, 23 May 2020 15:35:36 +0500
> Subject: [PATCH] CLEANUP: src/checks.c: ignore return value using DISGUISE(..)
>
> we do not want to check status of extchk_setenv, but static analyzsers
>
Le 26/05/2020 à 08:56, Willy Tarreau a écrit :
Hi Joao,
On Thu, May 21, 2020 at 09:41:19PM -0300, Joao Morais wrote:
Hello list, the 401 is one of the http status code haproxy generates itself:
https://github.com/haproxy/haproxy/blob/v2.1.0/doc/configuration.txt#L363
This cannot
Hi Willy,
On Tue, May 26, 2020 at 4:31 PM Willy Tarreau wrote:
> Hi Igor,
>
> On Sun, May 24, 2020 at 10:35:10AM +1000, Igor Cicimov wrote:
> > Hi guys,
> >
> > We are getting segfaults with haproxy 1.8.25 and thought I would ask if
> > this rings any bell:
> >
> > segfault at 5609a853 ip
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses
Hi Willy,
On Tue, May 26, 2020 at 4:43 PM Willy Tarreau wrote:
> On Sun, May 24, 2020 at 10:35:10AM +1000, Igor Cicimov wrote:
> > We are getting segfaults with haproxy 1.8.25
>
> By the way, does this mean you didn't get them with a previous version
> (presumably 1.8.24) ? There aren't that
On Wed, May 27, 2020 at 11:48:05AM +1000, Igor Cicimov wrote:
> Hi Willy,
>
> On Tue, May 26, 2020 at 4:43 PM Willy Tarreau wrote:
>
> > On Sun, May 24, 2020 at 10:35:10AM +1000, Igor Cicimov wrote:
> > > We are getting segfaults with haproxy 1.8.25
> >
> > By the way, does this mean you didn't
11 matches
Mail list logo
