Re: haproxy -v doesn't show commit used when building from 2.0 repository?

On Thu, Aug 01, 2019 at 08:41:22PM +0200, PiBa-NL wrote: > Works for me, building latest commit in 2.0 repository now haproxy -v shows: > "HA-Proxy version 2.0.3-7343c71 2019/08/01 - https://haproxy.org/; for me. > Thanks for your quick fix :). Ah great, thanks for confirming! Willy

Re: haproxy -v doesn't show commit used when building from 2.0 repository?

Hi Willy, Op 1-8-2019 om 6:21 schreef Willy Tarreau: Hi Pieter, On Wed, Jul 31, 2019 at 10:56:54PM +0200, PiBa-NL wrote: Hi List, I have build haproxy 2.0.3-0ff395c from sources however after running a 'haproxy -v' it shows up as: 'HA-Proxy version 2.0.3 2019/07/23 - https://haproxy.org/'

Re: Recent BoringSSL build breakage

On Thu, Aug 01, 2019 at 11:17:36AM +0200, Emmanuel Hocdet wrote: > Yep, i already built with the change. Fix included. Now pushed, thank you! Let's hope all checks turn green now. > I'm looking at BORINGSSL_API_VERSION for compatibility evolution, but for now > is not incremented as i would

Re: Coverity scans?

also, I've no idea what to specify in COVERITY_SCAN_NOTIFICATION_EMAIL (which is mandatory) чт, 1 авг. 2019 г. в 12:32, Dinko Korunic : > Hey Илья, > > Looks fine and clean. I guess that we would use existing project name > (Haproxy) or you would like to continue with your own? > > Last, I

Re: [PATCH] BUG/MAJOR: http/sample: use a static buffer for raw -> htx conversion

Le 01/08/2019 à 06:17, Willy Tarreau a écrit : Hi Richard, On Wed, Jul 31, 2019 at 02:03:26PM -0700, Richard Russo wrote: I've attached a patch to fix a bug in http sampling on raw connections. This fixes crashes experienced with a frontend configuration similar to: frontend haproxy_v4_http_0

Re: Recent BoringSSL build breakage

Hi Willy,Le 1 août 2019 à 10:07, Willy Tarreau a écrit :Hi Manu,On Travis CI there was a fairly recent regression on BoringSSL whichhappened between 03e09f3 and a7a0f99 a day ago. It breaks on definitionof EVP_PKEY_base_id() in openssl-compat.h, which was not modified, andI guess

Re: Coverity scans?

чт, 1 авг. 2019 г. в 12:32, Dinko Korunic : > Hey Илья, > > Looks fine and clean. I guess that we would use existing project name > (Haproxy) or you would like to continue with your own? > I would move to "haproxy/haproxy" however, proper token must be set in travis-ci environment (if token is

Re: [PATCH] BUG/MAJOR: http/sample: use a static buffer for raw -> htx conversion

Le 01/08/2019 à 11:17, Christopher Faulet a écrit : Le 01/08/2019 à 06:17, Willy Tarreau a écrit : Hi Richard, On Wed, Jul 31, 2019 at 02:03:26PM -0700, Richard Russo wrote: I've attached a patch to fix a bug in http sampling on raw connections. This fixes crashes experienced with a frontend

Re: Coverity scans?

Hi Илья, Haproxy Coverity project token is: 9Zw8bB4a Given that it’s per-project token, that can be hardcoded in TravisCI configuration without any issues. In regards to notification mails, well for now I think that can have your and my mail for now until we think of something better. Willy,

Re: Coverity scans?

чт, 1 авг. 2019 г. в 15:23, Dinko Korunic : > Hi Илья, > > Haproxy Coverity project token is: 9Zw8bB4a > Given that it’s per-project token, that can be hardcoded in TravisCI > configuration without any issues. > > In regards to notification mails, well for now I think that can have your > and my

Re: Coverity scans?

Hey Илья, Looks fine and clean. I guess that we would use existing project name (Haproxy) or you would like to continue with your own? Last, I wonder do we really need verbose (V=1) builds and do you think if they make sense for Coverity builds? Thanks, D. > On 30 Jul 2019, at 10:35, Илья

Recent BoringSSL build breakage

Hi Manu, On Travis CI there was a fairly recent regression on BoringSSL which happened between 03e09f3 and a7a0f99 a day ago. It breaks on definition of EVP_PKEY_base_id() in openssl-compat.h, which was not modified, and I guess this issue was hidden by the simultaneous breakage of libressl by

Re: Coverity scans?

Dinko, Am 01.08.19 um 12:20 schrieb Dinko Korunic: > Haproxy Coverity project token is: *snip* > Given that it’s per-project token, that can be hardcoded in TravisCI > configuration without any issues. I'm not sure if the token is meant to kept secret, but I wanted to let you know that you sent