On Tue, Mar 17, 2020 at 09:08:24PM +0100, Tim Duesterhus wrote:
> The behavior of calloc() when being passed `0` as `nelem` is implementation
> defined. It may return a NULL pointer.
>
> Avoid this issue by checking before allocating. While doing so adjust the
> local
> integer variables that
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
The behavior of calloc() when being passed `0` as `nelem` is implementation
defined. It may return a NULL pointer.
Avoid this issue by checking before allocating. While doing so adjust the local
integer variables that are used to refer to memory offsets to `size_t`.
This issue was introced in
Hello,
it is not trivial bash redirection misuse fix.
Cheers,
Ilya Shipitcin
From d405c779f1c9e5b37532d0ac95e441a0735899bb Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Tue, 17 Mar 2020 20:57:25 +0500
Subject: [PATCH] CI: proper group output redirection together with travis_wait
The only place tcp-request appears in my config is in relation to
rate-limiting, which we have set up to track but not enforce. Here are the
associated rules:
frontend main
[...]
acl rate_whitelist src 10.0.0.1
acl rate_whitelist src 10.0.1.1
acl rate_whitelist src 10.0.1.2
Le 13/03/2020 à 08:02, Kevin Zhu a écrit :
Hi again
In version 2.1.3:
When config spoe engine proxys > 1, the function "srandom" will run more
than one times, it will make some engine_id duplicated, and the SPOA
is group SPOP connections by engine_id when option async is on, the
ack will reply
Le 06/03/2020 à 18:53, Sean Reifschneider a écrit :
Here's what the stack traces look like, they all seem to be showing
"pattern_exec_match" and "epool_wait":
PID: 14348 (haproxy)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Thu
7 matches
Mail list logo
