Re: [PR] avoid overriding external prefix

2018-01-04 2:13 GMT+05:00 Willy Tarreau : > Hi Stephen, > > On Wed, Jan 03, 2018 at 08:33:14PM +0100, PR Bot wrote: > > Dear list! > > > > Author: Stephen > > Number of patches: 1 > > > > This is an automated relay of the Github pull request: >

Re: centos packages built

Did you try fedora copr? On Dec 26, 2017 9:50 PM, "Angelo Hongens" wrote: > > FYI, I built haproxy packages for centos6 and centos7, and intend to keep > the repo up to date. I run haproxy on dozens of machines, and I manage them > using spacewalk. So I want recent RPM's ;)

Re: Re[2]: CI/CD HAProxy

2017-12-15 13:07 GMT+05:00 Aleksandar Lazic <al-hapr...@none.at>: > Hi > > -- Originalnachricht -- > Von: "Илья Шипицин" <chipits...@gmail.com> > An: "Aleksandar Lazic" <al-hapr...@none.at> > Cc: "Olivier Doucet" <

Re: CI/CD HAProxy

2017-09-16 20:01 GMT+05:00 Aleksandar Lazic : > Hi Olivie. > > Olivier Doucet wrote on 15.09.2017: > > > Hi, > > > > I wanted to open a new thread, as "cppcheck finding" was hijacked with > this CICD / testing ;) > > +1 > > > I think the best is the enemy of the good : why not

Re: HAProxy LB causes server to poll for request data for a long time

Try proxy_buffering off; proxy_request_buffering off; in nginx On Nov 15, 2017 8:01 PM, "omer kirkagaclioglu" wrote: Hi, I just put a service that has around 400 - 4K http / https mixed requests per second behind haproxy. The endpoint with the highest rate of requests

Re: Experimental / broken HTTP/2 support

2017-10-15 23:43 GMT+05:00 Willy Tarreau : > On Sun, Oct 15, 2017 at 07:16:51PM +0100, Aaron West wrote: > > Hi Willy, > > > > Sorry to bother you, just a quick question if I may. > > > > Does support for QUIC imply we'd have rudimentary UDP support as well > > or is it only going to

Re: patch: allow to use any compiler

2017-10-09 10:10 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 9 octobre 2017 08:49 +0500, Илья Шипицин <chipits...@gmail.com> : > > >> > any particular reason for mixing "CC=gcc" with "CC?=gcc" ? > >> > &g

Re: patch: allow to use any compiler

2017-10-08 15:59 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 8 octobre 2017 15:46 +0500, Илья Шипицин <chipits...@gmail.com> : > > >> > while some Makefiles allow to use CC, other just stick to gcc. > >> > I think we should change to > >&g

Re: patch: allow to use any compiler

2017-10-05 1:01 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 4 octobre 2017 23:49 +0500, Илья Шипицин <chipits...@gmail.com> : > > > while some Makefiles allow to use CC, other just stick to gcc. > > I think we should change to > > > > CC ?= gcc >

Re: patch: allow to use any compiler

2017-10-05 1:01 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 4 octobre 2017 23:49 +0500, Илья Шипицин <chipits...@gmail.com> : > > > while some Makefiles allow to use CC, other just stick to gcc. > > I think we should change to > > > > CC ?= gcc >

patch: allow to use any compiler

Hello, while some Makefiles allow to use CC, other just stick to gcc. I think we should change to CC ?= gcc everywhere Cheers, Ilya Shipitsin From 246341f636d085a4e99bdc9f66b5fa3c7bb2b7d3 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 4 Oct 2017 23:43:05 +0500

Re: another cppcheck finding

2017-10-04 14:00 GMT+05:00 Christopher Faulet <cfau...@haproxy.com>: > Le 04/10/2017 à 07:49, Илья Шипицин a écrit : > >> >> >> 2017-10-04 9:15 GMT+05:00 Willy Tarreau <w...@1wt.eu <mailto:w...@1wt.eu>>: >> >> Hi Ilya, >> >>

Re: another cppcheck finding

2017-10-04 9:15 GMT+05:00 Willy Tarreau : > Hi Ilya, > > [also CCing Baptiste] > > On Tue, Oct 03, 2017 at 05:25:17PM +0500, ??? wrote: > > [src/dns.c:2502]: (error) Memory leak: buffer > > > > > > I do not see any "buffer" usage except conditional free. > > should we just

another cppcheck finding

hello! [src/dns.c:2502]: (error) Memory leak: buffer I do not see any "buffer" usage except conditional free. should we just remove "buffer" from there ? Cheers, Ilya Shipitsin

Re: resolve memory leak in contrib/halog/halog.c

Ack/Nack ? 22 сент. 2017 г. 22:44 пользователь "Илья Шипицин" <chipits...@gmail.com> написал: > Hello, > > > [contrib/halog/halog.c:1572]: (error) Memory leak: ustat >

Re: Haproxy segfault error 4 in libc-2.24

you can try to attach like that https://stackoverflow.com/questions/2152582/start-gdb-using-a-pid (I still think, that core dump is better if possible) 2017-10-02 21:59 GMT+05:00 Marcus Ulbrich : > no chance... error or killing haproxy there is no core file

resolve memory leak in contrib/halog/halog.c

Hello, [contrib/halog/halog.c:1572]: (error) Memory leak: ustat From e58f1f8989715b2fa0c47c9169985d665c32c487 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Fri, 22 Sep 2017 22:33:16 +0500 Subject: [PATCH] BUG/MINOR: contrib/halog: fixing small memory leak Issue was

Re: more cppcheck findings

hello, in case someone is interested, the full list of cppcheck findings git clone http://git.haproxy.org/git/haproxy.git/ cd haproxy script cppcheck --force --enable=all . Ctrl-D grep '(error' typescript grep '(warning' typescript grep '(style' typescript | grep 'The function ' | grep ' is

more cppcheck findings

hello, [contrib/halog/halog.c:1572]: (error) Memory leak: ustat [contrib/mod_defender/defender.c:153]: (error) va_list 'argp' was opened but not closed by va_end(). [contrib/modsecurity/modsec_wrapper.c:109]: (error) va_list 'ap' was opened but not closed by va_end(). [src/51d.c:373]: (error)

Re: cppcheck finding

2017-09-15 21:29 GMT+05:00 Aleksandar Lazic : > Hi. > > Willy Tarreau wrote on 15.09.2017: > > > On Fri, Sep 15, 2017 at 06:36:20PM +0500, ??? wrote: > >> I'd say, it's chicken and egg situation. Whichever comes first, tests > or CI. > >> if we start a CI with "just

Re: cppcheck finding

2017-09-15 18:22 GMT+05:00 Christopher Faulet <cfau...@haproxy.com>: > Le 15/09/2017 à 15:07, Илья Шипицин a écrit : > >> and what about CI ? >> >> something like gitlab-ci, travis, jenkins ? I'll invest some efforts in >> that >> >> > No CI. T

Re: cppcheck finding

and what about CI ? something like gitlab-ci, travis, jenkins ? I'll invest some efforts in that 2017-09-15 18:04 GMT+05:00 Christopher Faulet <cfau...@haproxy.com>: > Le 15/09/2017 à 08:36, Илья Шипицин a écrit : > >> great, thank for the feedback. >> >

Re: cppcheck finding

great, thank for the feedback. there're few things like that [src/flt_http_comp.c:926] -> [src/flt_http_comp.c:926]: (warning) Either the condition 'txn' is redundant or there is possible null pointer dereference: txn. [src/flt_spoe.c:2765] -> [src/flt_spoe.c:2766]: (warning) Either the

cppcheck finding

hello, [src/flt_http_comp.c:926] -> [src/flt_http_comp.c:926]: (warning) Either the condition 'txn' is redundant or there is possible null pointer dereference: txn. should there be && instead of || ? Cheers, Ilya Shipitsin

Re: dynamic configuration via DNS SRV records

2016-12-19 5:43 GMT+05:00 jerry : > Hi, > > We use haproxy quite a but at soundhound for fronting our various external > and internal services. We are i the process of moving to a container based > deployment model. With kubernetes in particular, it's as easy as editing 1 >

Re: clang static analysis of haproxy

2016-10-26 13:26 GMT+05:00 Willy Tarreau : > On Wed, Oct 26, 2016 at 01:15:43PM +0500, ?? wrote: > > as time goes on ... I see, haproxy moved to github ? > > No, it's another fork dedicated to travis that causes some confusion > and that we're trying to smoothly

Re: clang static analysis of haproxy

as time goes on ... I see, haproxy moved to github ? I like github, especially for PR and travis. should I open a PR on those (not very critial) issues ? and what do you think of travis-ci ? I have some experience in using it, very nice. 2016-06-07 15:20 GMT+05:00 Willy Tarreau :

Re: clang static analysis of haproxy

hould be freed if args[2] is neither "request" nor "response", > otherwise the allocated address is permanently forgotten. > > > On Mon, Jun 6, 2016 at 12:52 PM, Maciej Katafiasz > <mkatafi...@purestorage.com> wrote: > > On 6 June 2016

clang static analysis of haproxy

Hello, I run scan-build (which is clang static analysis tool) on haproxy git source here's result http://chipitsine.github.io/haproxy-1.7-dev/ there some null pointer dereferences and memory leaks, I think worth looking at them. also, is there some bug tracker ? CI (like travis-ci or

how to perform 2 healthcheck at once ?

Dear Sirs, we are running haproxy for SSL balancing using tcp mode clusters. and we are using http checks. actual config is: listen cluster.auth 0.0.0.0:443 mode tcp option tcpka option httpchk GET /ping.ashx HTTP/1.0 balance source server front-1 x.y.z.t:443 check port 80

how to perform 2 healthcheck at once ?

Dear Sirs, we are running haproxy for SSL balancing using tcp mode clusters. and we are using http checks. actual config is: listen cluster.auth 0.0.0.0:443 mode tcp option tcpka option httpchk GET /ping.ashx HTTP/1.0 balance source server front-1 x.y.z.t:443 check port 80 inter

<    7   8   9   10   11   12