freebsd builds are broken for few days

2019-10-13 Thread Илья Шипицин
https://cirrus-ci.com/github/haproxy/haproxy I'll bisect if noone else knows what's going on

"official" rpm repo ?

2019-10-08 Thread Илья Шипицин
hi, I played a bit with Fedora COPR (it is nice) https://copr.fedorainfracloud.org/coprs/chipitsine/haproxy/build/1041926/ few questions 1) do we insist on Lua support ? (it is hard to get Lua-5.3 for EPEL7) 2) any best practice on building new packages ? anyway, I do not insist in running

using hashicorp vault for storing SSL certs

2019-09-29 Thread Илья Шипицин
hello, is anybody using https://www.vaultproject.io/docs/secrets/pki/index.html for storing certs ? (I want to avoid reinventing the wheel here) thanks, Ilya Shipitcin

Re: [PATCH] improving github experience, kindly ask people to reproduce bugs on latest haproxy

2019-09-23 Thread Илья Шипицин
пн, 23 сент. 2019 г. в 22:02, Willy Tarreau : > Hi guys, > > On Fri, Sep 20, 2019 at 03:47:17PM +0200, Lukas Tribus wrote: > > Hello Patrick, > > > > > > > I dunno, I've personally never been fond of it when bug reporters are > blindly asked to upgrade to the latest version. > > > > Everything

[PATCH] improving github experience, kindly ask people to reproduce bugs on latest haproxy

2019-09-19 Thread Илья Шипицин
hello, please find attached patch Ilya Shipitsin From 2d4b8bf119bf470c2c607a1fd22cee8267e6843b Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Fri, 20 Sep 2019 00:07:11 +0500 Subject: [PATCH] DOC: kindly ask people whether they run latest HAProxy --- .github/ISSUE_TEMPLATE/Bug.md | 4

[PATCH] enabling slz, pcre2 builds in travis-ci

2019-09-19 Thread Илья Шипицин
hello, please consider attached patch Ilya Shipitsin From b65dc30f1c07aca067ebb31d373833fe66486b7b Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Thu, 19 Sep 2019 23:32:30 +0500 Subject: [PATCH] BUILD: travis-ci: add PCRE2, SLZ build --- .travis.yml | 9 - 1 file changed, 8

Re: PATCH: install golang-1.13 during travis-ci build as it is required for BoringSSL

2019-09-17 Thread Илья Шипицин
Willy, can you apply this ? boringssl builds are bloody murder пн, 16 сент. 2019 г. в 16:14, Илья Шипицин : > please see attached patch >

PATCH: install golang-1.13 during travis-ci build as it is required for BoringSSL

2019-09-16 Thread Илья Шипицин
please see attached patch From 5fa12aec93f1e8989e06628fc5e41fc2556f532b Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Mon, 16 Sep 2019 16:13:10 +0500 Subject: [PATCH] BUILD: CI: install golang-1.13 when building BoringSSL --- scripts/build-ssl.sh | 4 1 file changed, 4 insertions(+)

Re: Linux Builds broken on Travis CI

2019-09-14 Thread Илья Шипицин
it turned out that ASAN is "the root cause" of those failures. let us disable it for a while (I attached patch) пт, 13 сент. 2019 г. в 19:23, Илья Шипицин : > > > On Fri, Sep 13, 2019, 3:49 PM Willy Tarreau wrote: > >> On Fri, Sep 13, 2019 at 03:45:21PM +0500, ?

Re: Linux Builds broken on Travis CI

2019-09-13 Thread Илья Шипицин
On Fri, Sep 13, 2019, 3:49 PM Willy Tarreau wrote: > On Fri, Sep 13, 2019 at 03:45:21PM +0500, ??? wrote: > > now build fails with > > > > "** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for > > thread 1." > > That's exactly the issues I was talking about that

Re: Linux Builds broken on Travis CI

2019-09-13 Thread Илья Шипицин
now build fails with "** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for thread 1." no more failures due to leaks. пт, 13 сент. 2019 г. в 13:33, Willy Tarreau : > On Fri, Sep 13, 2019 at 01:23:12PM +0500, ??? wrote: > > Build was failed due to memory leak

Re: Linux Builds broken on Travis CI

2019-09-13 Thread Илья Шипицин
Build was failed due to memory leak detected by asan https://github.com/haproxy/haproxy/issues/256 I think we can change the way asan works, I.e. log errors and do not stop tests On Fri, Sep 13, 2019, 7:59 AM Willy Tarreau wrote: > Hi Tim, > > On Fri, Sep 06, 2019 at 04:30:24PM +0200, Tim

Re: Docker Image update to OpenSSL 1.1.1d

2019-09-11 Thread Илья Шипицин
чт, 12 сент. 2019 г. в 01:01, Aleksandar Lazic : > Hi. > > Am 11.09.2019 um 20:48 schrieb Илья Шипицин: > > Hello, > > > > it was a surprize for me that official images are also available (I used > to > > think your images are only available) >

Re: Docker Image update to OpenSSL 1.1.1d

2019-09-11 Thread Илья Шипицин
oops. I did have a look at https://hub.docker.com/search?q=haproxytech=image (built from https://github.com/haproxytech ) so... there are many many many docker images. when should I use either of these images? ср, 11 сент. 2019 г. в 23:48, Илья Шипицин : > Hello, > > it was a surpri

Re: Docker Image update to OpenSSL 1.1.1d

2019-09-11 Thread Илья Шипицин
Hello, it was a surprize for me that official images are also available (I used to think your images are only available) https://hub.docker.com/_/haproxy is there some documentation when your images should be used (instead of official) ? ср, 11 сент. 2019 г. в 22:58, Aleksandar Lazic : > Hi.

Re: Coverity scan findings

2019-09-11 Thread Илья Шипицин
it depends on how haproxy is built (number of flags) we use most of available options when testing on coverity https://github.com/haproxy/haproxy/blob/master/.travis.yml#L8 can you share build command ? we may also set up sonar in travis-ci schedules. (personally, I find sonar too much noisy,

Re: [PATCH] basic CentOS6 CI

2019-09-08 Thread Илья Шипицин
Good good good. On Sun, Sep 8, 2019, 3:11 PM Willy Tarreau wrote: > On Fri, Sep 06, 2019 at 11:24:44PM +0500, ??? wrote: > > here's another CI patch (which skips alpn testing on CentOS 6) > > Thanks Ilya, I've merged it and added a commit message based on the > explanation in the

Re: [PATCH] basic CentOS6 CI

2019-09-06 Thread Илья Шипицин
hello, here's another CI patch (which skips alpn testing on CentOS 6) пт, 6 сент. 2019 г. в 15:48, Илья Шипицин : > great. > > I'll resolve ALPN testing soon. let those builds be red for a while. > > пт, 6 сент. 2019 г. в 14:45, Willy Tarreau : > >> On Mon, Sep 02,

Re: [PATCH] basic CentOS6 CI

2019-09-06 Thread Илья Шипицин
great. I'll resolve ALPN testing soon. let those builds be red for a while. пт, 6 сент. 2019 г. в 14:45, Willy Tarreau : > On Mon, Sep 02, 2019 at 12:10:11AM +0500, ??? wrote: > > please review the following patch > > No particular opinion on it so I merged it. > > Thanks Ilya. > Willy

Re: [PATCH] basic CentOS6 CI

2019-09-05 Thread Илья Шипицин
hi, any update ? пн, 2 сент. 2019 г. в 10:56, Илья Шипицин : > any idea how to skip "alpn" test on CentOS 6 ? > > (I think, I should "rm" particular reg test, however, it does not look > nice) > > пн, 2 сент. 2019 г. в 00:10, Илья Шипицин : > >> please review the following patch >> >

Re: [PATCH] basic CentOS6 CI

2019-09-01 Thread Илья Шипицин
any idea how to skip "alpn" test on CentOS 6 ? (I think, I should "rm" particular reg test, however, it does not look nice) пн, 2 сент. 2019 г. в 00:10, Илья Шипицин : > please review the following patch >

[PATCH] basic CentOS6 CI

2019-09-01 Thread Илья Шипицин
please review the following patch From 18407b76821713b44f2fc5a8fa0e63635d454651 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Mon, 2 Sep 2019 00:03:10 +0500 Subject: [PATCH] BUILD: CI: add basic CentOS 6 cirrus build --- .cirrus.yml | 13 + 1 file changed, 13 insertions(+)

does anybody knows something about https://gitlab.com/haproxy ?

2019-08-30 Thread Илья Шипицин

Re: PATCH: save some electricity on travis-ci (run non mainstream builds only daily)

2019-08-19 Thread Илья Шипицин
sure. I attached new patch пн, 19 авг. 2019 г. в 11:48, Willy Tarreau : > On Sun, Aug 18, 2019 at 02:25:00PM +0500, ??? wrote: > > Hi, any update on this? > > Sorry, I wanted to comment on it then got distracted by other activities. > Could you please put a commit message roughly

Re: PATCH: save some electricity on travis-ci (run non mainstream builds only daily)

2019-08-18 Thread Илья Шипицин
Hi, any update on this? On Wed, Aug 7, 2019, 7:10 PM Илья Шипицин wrote: > Hello, > > please find attached patch. > > > Thanks! > Ilya Shipitsin >

any official rpm (centos, fedora) repo ?

2019-08-17 Thread Илья Шипицин
Hello, is there any official repo ? (I could not find one) Ilya Shipitsin

Re: [PATCH 1/1] DOC: Add 'Question.md' issue template, discouraging asking questions

2019-08-11 Thread Илья Шипицин
Tim, what do you think of providing some info on _first_ issue? Look, what I've accidently found :) https://github.com/actions/starter-workflows/blob/master/automation/greetings.yml On Fri, Aug 2, 2019, 10:16 PM Willy Tarreau wrote: > On Fri, Aug 02, 2019 at 03:10:11PM +0200, Lukas Tribus

PATCH: save some electricity on travis-ci (run non mainstream builds only daily)

2019-08-07 Thread Илья Шипицин
Hello, please find attached patch. Thanks! Ilya Shipitsin From 4331513404b73b760e0095b09893a226bd30b574 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 7 Aug 2019 18:51:24 +0500 Subject: [PATCH] BUILD: travis-ci: trigger non-mainstream configurations only on daily builds. Let us save

Re: patch: enable Coverity scan in travis-ci builds

2019-08-07 Thread Илья Шипицин
ср, 7 авг. 2019 г. в 13:45, Willy Tarreau : > On Wed, Aug 07, 2019 at 01:15:28PM +0500, ??? wrote: > > btw, Willy, we can exclude some exotic build targets from "on push" to > "on > > cron" > > > > by changing "if: type != cron" --> "if: type == cron" > > > > > > probably boringssl,

Re: patch: enable Coverity scan in travis-ci builds

2019-08-07 Thread Илья Шипицин
btw, Willy, we can exclude some exotic build targets from "on push" to "on cron" by changing "if: type != cron" --> "if: type == cron" probably boringssl, cygwin, libressl ? ср, 7 авг. 2019 г. в 12:07, Willy Tarreau : > Hi Ilya, > > On Tue, Aug 06, 2019 at 10:55:47AM +0500, ???

Re: patch: enable Coverity scan in travis-ci builds

2019-08-07 Thread Илья Шипицин
Dinko, can you please disable your schedule (is it cron or whatever) ? ср, 7 авг. 2019 г. в 12:07, Willy Tarreau : > Hi Ilya, > > On Tue, Aug 06, 2019 at 10:55:47AM +0500, ??? wrote: > > 1) follow to https://travis-ci.com/haproxy/haproxy/settings > > > > > > 2) setup COVERITY_SCAN_TOKEN

Re: patch: enable Coverity scan in travis-ci builds

2019-08-06 Thread Илья Шипицин
oops, I forgot to remove list. Dinko, can you please generate new token ? вт, 6 авг. 2019 г. в 10:55, Илья Шипицин : > great! > > > next steps > > 1) follow to https://travis-ci.com/haproxy/haproxy/settings > > > 2) setup COVERITY_SCAN_TOKEN = P6rHpv1618gwKW

Re: patch: enable Coverity scan in travis-ci builds

2019-08-05 Thread Илья Шипицин
great! next steps 1) follow to https://travis-ci.com/haproxy/haproxy/settings 2) setup COVERITY_SCAN_TOKEN = P6rHpv1618gwKWkVs7FfKQ 3) setup daily schedule (screen attached) вт, 6 авг. 2019 г. в 09:42, Willy Tarreau : > Hi Ilya, Dinko, > > On Fri, Aug 02, 2019 at 11:04:30PM +0500,

patch: enable Coverity scan in travis-ci builds

2019-08-02 Thread Илья Шипицин
Hello, please find attached patch. it enables coverity scans. also, couple of things need to be done within travis-ci: 1) specify daily schedule 2) specify coverity scan token (Dinko will provide it off list) thanks! Ilya Shipitsin From 9c7e0bcec2629f7cf128254c1bb1e8cdccc723cb Mon Sep 17

Re: Coverity scans?

2019-08-01 Thread Илья Шипицин
quot;null pointer deerefence is resolved" Coverity is very good in catching null pointer derefence (even if we do not know how it might be exploited). Currently, haproxy has tens of them unresolved. > > > Kind regards, > D. > > > On 1 Aug 2019, at 11:59, Илья Шипицин w

Re: Coverity scans?

2019-08-01 Thread Илья Шипицин
> > 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, Илья Шипицин wrote: > > Dinko, > > please have a look > > https://github.com/chipitsine/ha

Re: Coverity scans?

2019-08-01 Thread Илья Шипицин
-ci environment (if token is not set, build is skipped) > > Last, I wonder do we really need verbose (V=1) builds and do you think if > they make sense for Coverity builds? > I'll polish it for a few days and will submit a patch > > > Thanks, > D. > > On 30 Jul 2019, at

Re: Coverity scans?

2019-07-30 Thread Илья Шипицин
cess required for doing so right now. > > > Kind regards, > D. > > On 17 Jul 2019, at 13:18, Илья Шипицин wrote: > > Hello, yep, contributor/member would be nice. Also, I can setup automated > travis-ci scans > > On Wed, Jul 17, 2019, 3:27 PM Dinko Korunic > wrote: &g

PATCH: fix possible null pointer dereference

2019-07-25 Thread Илья Шипицин
hello, it was found by Coverity From bac4e3e88260bab3db6650f43ac53a1e2771242e Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Thu, 25 Jul 2019 16:47:58 +0500 Subject: [PATCH] src/checks.c: resolve possible null pointer dereference found by Coverity --- src/checks.c | 2 +- 1 file changed,

Re: FreeBSD CI builds fail

2019-07-24 Thread Илья Шипицин
ср, 24 июл. 2019 г. в 08:55, Willy Tarreau : > Hi guys, > > On Tue, Jul 23, 2019 at 08:37:37PM +0200, Jerome Magnin wrote: > > On Tue, Jul 23, 2019 at 07:09:57PM +0200, Tim Düsterhus wrote: > > > Jérôme, > > > Ilya, > > > > > > I noticed that FreeBSD CI fails since > > > >

reg-tests/checks/tcp-check_multiple_ports.vtc fails on FreeBSD

2019-07-23 Thread Илья Шипицин
can someone have a look ? https://cirrus-ci.com/task/5737816791711744

Re: Coverity scans?

2019-07-21 Thread Илья Шипицин
ty Scan > account and they well, require manual interventions, flagging and some day > to day work to get to more usable levels — let me know if you need a hand > with this. You should have all the access required for doing so right now. > > > Kind regards, > D. > > On 17 J

Re: Coverity scans?

2019-07-17 Thread Илья Шипицин
volved and I have started > configuring modules and parts of code blocks into coherent units, but > stopped at some point due to lack of time and interest. > > There have been a lot of false positives however, I dare to say even in > excessive volumes. > > > On 17 Jul

Coverity scans?

2019-07-16 Thread Илья Шипицин
Hello, I played with Coverity. Definitely it shows "issues resolved" after bugfixes pushed to git. I know Willy does not like static analysis because of noise. Anyway, it finds bugs, why not to use it?

building haproxy against openssl no-deprecated

2019-07-15 Thread Илья Шипицин
Hello, I tried to build openssl-1.1.1 with "no-deprecated" src/ssl_sock.o: In function `ssl_sock_do_create_cert': /home/travis/build/chipitsine/haproxy/src/ssl_sock.c:1867: undefined reference to `X509_get_notBefore' /home/travis/build/chipitsine/haproxy/src/ssl_sock.c:1868: undefined reference

Re: [PATCH v2] BUG/MINOR: ssl: revert empty handshake detection in OpenSSL <= 1.0.2

2019-07-08 Thread Илья Шипицин
Nice On Mon, Jul 8, 2019, 5:30 PM Lukas Tribus wrote: > Commit 54832b97 ("BUILD: enable several LibreSSL hacks, including") > changed empty handshake detection in OpenSSL <= 1.0.2 and LibreSSL, > from accessing packet_length directly (not available in LibreSSL) to > calling SSL_state() instead.

Re: [RFC PATCH] BUG/MINOR: ssl: revert empty handshake detection in OpenSSL <= 1.0.2

2019-07-06 Thread Илья Шипицин
сб, 6 июл. 2019 г. в 16:09, Willy Tarreau : > hi Guys, > > On Fri, Jul 05, 2019 at 05:07:27PM +0200, Emmanuel Hocdet wrote: > > > > > Le 4 juil. 2019 à 18:55, ??? a écrit : > > > > > > can you provide some comment around code ? > > > > > > I think almost nobody can read such code > > >

Re: [RFC PATCH] BUG/MINOR: ssl: revert empty handshake detection in OpenSSL <= 1.0.2

2019-07-04 Thread Илья Шипицин
conn->err_code = CO_ER_SSL_EMPTY; > *else* > conn->err_code = CO_ER_SSL_ABORT; > > ++ > Manu > > Le 4 juil. 2019 à 12:14, Lukas Tribus a écrit : > > Hello Ilya, > > > On Mon, 1 Jul 2019 at 23:08, Илья Шипицин wrote: > > > &

Re: Error with AddressSanitizer

2019-07-04 Thread Илья Шипицин
did you also use USE_OBSOLETE_LINKER=1 ? asan is supposed to be used together with obsolete linking чт, 4 июл. 2019 г. в 19:14, : > Hi > > I got this error when trying to debug a problem in haproxy > > compile haproxy using clang with -fsanitize=address and start haproxy: > > >

Re: [RFC PATCH] BUG/MINOR: ssl: revert empty handshake detection in OpenSSL <= 1.0.2

2019-07-01 Thread Илья Шипицин
вт, 2 июл. 2019 г. в 01:34, Willy Tarreau : > On Mon, Jul 01, 2019 at 10:32:29PM +0200, Lukas Tribus wrote: > > Commit 54832b97 ("BUILD: enable several LibreSSL hacks, including") > > changed empty handshake detection in OpenSSL <= 1.0.2 and LibreSSL, > > from accessing packet_length directly

Re: [PR] BUILD: extend travis-ci matrix

2019-07-01 Thread Илья Шипицин
wow. I am surprised how proxy protocl might be used. can we add reg test on that ? вт, 2 июл. 2019 г. в 01:31, Lukas Tribus : > Hello Ilya, hello Willy, > > > On Thu, 27 Jun 2019 at 14:04, Lukas Tribus wrote: > > > > Hello, > > > > On Thu, 27 Jun 2019 at 13:19, Willy Tarreau wrote: > > > > > >

Re: [PR] BUILD: extend travis-ci matrix

2019-06-27 Thread Илья Шипицин
чт, 27 июн. 2019 г. в 15:33, Lukas Tribus : > Hello, > > On Thu, 27 Jun 2019 at 08:43, Илья Шипицин wrote: > >> However this commit also changes error handling with OpenSSL: > >> > >> > https://github.com/haproxy/haproxy/commit/54832b

Re: [PR] BUILD: extend travis-ci matrix

2019-06-27 Thread Илья Шипицин
ср, 26 июн. 2019 г. в 23:30, Lukas Tribus : > Hello Ilya, Willy, > > > On Sun, 5 May 2019 at 20:30, Илья Шипицин wrote: > > > > something has changed. build is passing now, reg-tests fail (they used > to work earlier) > > > > > > I'd apply those patc

Re: haproxy 2.0 - stretch - libgcc_s.so.1

2019-06-24 Thread Илья Шипицин
пн, 24 июн. 2019 г. в 22:08, Vincent Bernat : > ❦ 24 juin 2019 18:43 +02, Mildis : > > > I'm hitting > > https://www.mail-archive.com/haproxy@formilux.org/msg33189.html > > with haproxy 2.0 on Stretch, when doing a hot-reload > > > > Jun 24 18:34:05 haproxy[32347]: libgcc_s.so.1 must be

Re: haproxy 2.0 - stretch - libgcc_s.so.1

2019-06-24 Thread Илья Шипицин
Hello, who is Vincent ? and why are you asking the list about Vincent activities ? пн, 24 июн. 2019 г. в 21:47, Mildis : > Hi, > > I'm hitting > https://www.mail-archive.com/haproxy@formilux.org/msg33189.html > with haproxy 2.0 on Stretch, when doing a hot-reload > > Jun 24 18:34:05

Re: [PATCH 4/9] BUG/MINOR: mworker: Fix segmentation fault during cfgparse

2019-06-24 Thread Илья Шипицин
I had to be mroe detailed :) I meant "simple reg test" + address sanitizer which we run in travis address sanitizer is capable of catching those things пн, 24 июн. 2019 г. в 11:18, Илья Шипицин : > Does it make sense to also add regtest on that regression? > > On Mon, Jun 24

Re: [PATCH 4/9] BUG/MINOR: mworker: Fix segmentation fault during cfgparse

2019-06-24 Thread Илья Шипицин
Does it make sense to also add regtest on that regression? On Mon, Jun 24, 2019, 1:14 AM Tim Duesterhus wrote: > Consider this configuration: > > frontend fe_http > mode http > bind *:8080 > > default_backend be_http > > backend be_http > mode http >

travis-ci: split matrix into "cron" and "push" (move less popular builds to cron)

2019-06-16 Thread Илья Шипицин
hello, I played a bit with "if" condition https://github.com/chipitsine/haproxy/blob/master/.travis.yml in short, we can specify condition like that - os: osx if: type == cron compiler: clang env: TARGET=osx FLAGS="USE_OPENSSL=1" OPENSSL_VERSION=1.1.1c full list of conditions:

PATCH: travis-ci cleanup after build targets cleanup

2019-06-15 Thread Илья Шипицин
hello, we do not need to enable TFO and GETADDRINFO anymore in travis-ci builds. Ilya Shipitsin From cce91d6f2b6d22211d89f19e50c4b3addda27e34 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Sun, 16 Jun 2019 01:19:27 +0500 Subject: [PATCH] BUILD: travis-ci: TFO and GETADDRINFO are now

Re: Does anyone still use examples/haproxy.spec ?

2019-06-15 Thread Илья Шипицин
Examples might go to github wiki, for example On Sat, Jun 15, 2019, 8:49 PM Tim Düsterhus wrote: > Willy, > > Am 14.06.19 um 18:50 schrieb Willy Tarreau: > > Given that we're talking about one of our oldest files and that > > approximately no changes to it were made in the last 16 years, > >

memory sanitizer finding

2019-06-15 Thread Илья Шипицин
hello, *** h10.0 debug|==8132==WARNING: MemorySanitizer: use-of-uninitialized-value *** h10.0 debug|#0 0x7f37c06f1b60 (/usr/lib/x86_64-linux-gnu/liblua5.3.so.0+0x15b60) *** h10.0 debug|#1 0x7f37c06e355e in lua_pushstring (/usr/lib/x86_64-linux-gnu/liblua5.3.so.0+0x755e) ***

Re: Travis Matrix (was: Re: [PATCH] wurfl device detection build fixes and dummy library)

2019-06-13 Thread Илья Шипицин
пт, 14 июн. 2019 г. в 01:27, Willy Tarreau : > On Thu, Jun 13, 2019 at 10:28:19PM +0500, ??? wrote: > > > > or we can drop boringssl build in favour of Manu :) > > > > > > I suggest to drop BoringSSL. It's not intended to be used outside of > > > Google anyway. So if it breaks the user

Re: Travis Matrix (was: Re: [PATCH] wurfl device detection build fixes and dummy library)

2019-06-13 Thread Илья Шипицин
чт, 13 июн. 2019 г. в 22:25, Tim Düsterhus : > Ilya, > Willy, > > Am 13.06.19 um 19:11 schrieb Илья Шипицин: > > чт, 13 июн. 2019 г. в 22:07, Willy Tarreau : > > > >> On Thu, Jun 13, 2019 at 10:01:52PM +0500, ??? wrote: > >>> "everythin

Re: Travis Matrix (was: Re: [PATCH] wurfl device detection build fixes and dummy library)

2019-06-13 Thread Илья Шипицин
чт, 13 июн. 2019 г. в 22:07, Willy Tarreau : > On Thu, Jun 13, 2019 at 10:01:52PM +0500, ??? wrote: > > "everything enabled" is impossible. 51degrees may be enabled in two > > mutually exclusive ways. it doubles number of build configurations. > > It's not big deal, the haproxy-specific

Re: Travis Matrix (was: Re: [PATCH] wurfl device detection build fixes and dummy library)

2019-06-13 Thread Илья Шипицин
чт, 13 июн. 2019 г. в 21:28, Tim Düsterhus : > Ilya, > > (removed Ben and Christopher from Cc, as this no longer about 51d) > > Am 13.06.19 um 17:01 schrieb Илья Шипицин: > > please find "travis-ci + 51degree" patch attached. > > I'm unhappy with that pat

Re: Travis Matrix (was: Re: [PATCH] wurfl device detection build fixes and dummy library)

2019-06-13 Thread Илья Шипицин
чт, 13 июн. 2019 г. в 21:28, Tim Düsterhus : > Ilya, > > (removed Ben and Christopher from Cc, as this no longer about 51d) > > Am 13.06.19 um 17:01 schrieb Илья Шипицин: > > please find "travis-ci + 51degree" patch attached. > > I'm unhappy with that pat

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-06-13 Thread Илья Шипицин
Ben, I enabled "trie" on one build configuration and ... it failed https://travis-ci.com/haproxy/haproxy/jobs/207816969 it never failed before. can you have a look ? (also, it did NOT fail in my own fork) чт, 13 июн. 2019 г. в 20:03, Willy Tarreau : > On Thu, Jun 13, 2019 at 08:01:14PM +0500,

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-06-13 Thread Илья Шипицин
please find "travis-ci + 51degree" patch attached. чт, 13 июн. 2019 г. в 19:06, Willy Tarreau : > On Thu, Jun 13, 2019 at 02:02:33PM +, Ben Shillito wrote: > > Hi Willy, > > > > Yes, I agree the paths in the dummy library should match that of the > actual library. And yes, that patch is good

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-06-13 Thread Илья Шипицин
m/> > > O: +44 1183 287152 > E: b...@51degrees.com > @51Degrees <http://twitter.com/51Degreesmobi> > 51Degrees <https://www.linkedin.com/company/2171864> > > [image: Find out More] <https://51degrees.com/emailsig.aspx> > > > > *From:* Иль

Re: Idea + question regarding the build targets

2019-06-13 Thread Илья Шипицин
as for popular distro, for example fedora, I'd spent some time on packaging rpm in fedora copr (rather than telling people proper Makefile options). if there's an interest in "official" package distro, I'd take part with fedora copr and maybe few others ср, 12 июн. 2019 г. в 10:41, Willy Tarreau

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-06-13 Thread Илья Шипицин
running. > > > > Regards, > > > > Ben Shillito > Developer > > [image: 51Degrees] <https://51degrees.com/> > > O: +44 1183 287152 > E: b...@51degrees.com > @51Degrees <http://twitter.com/51Degreesmobi> > 51Degrees <https://www.linkedi

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-06-13 Thread Илья Шипицин
Ben, what is the proper way of building 51degree ? I added "USE_51DEGREES=1 51DEGREES_SRC=contrib/51d/src/pattern" (as I seen in documentation) gcc -Iinclude -Iebtree -Wall -Wextra -O2 -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv -Wno-unused-label -Wno-sign-compare

Re: cygwin compilation error

2019-06-05 Thread Илья Шипицин
Bob, we have added very basic cygwin CI https://travis-ci.com/haproxy/haproxy/jobs/205561046 it is "build only". feel free to improve it :) ср, 5 июн. 2019 г. в 02:49, Zakharychev, Bob : > Willy, > > On Tue, Jun 04, 2019 at 05:52:12PM +, Zakharychev, Bob wrote: > >> Finally got VTest

Re: [PATCH] CLEANUP: ssl: remove unneeded defined(OPENSSL_IS_BORINGSSL)

2019-06-05 Thread Илья Шипицин
something went wrong ? I do not see this commit ср, 5 июн. 2019 г. в 01:35, Willy Tarreau : > On Tue, Jun 04, 2019 at 05:04:03PM +0200, Emmanuel Hocdet wrote: > > Hi, > > > > Simple cleanup to limit #defined inflation. > > Merged, thanks Manu. > > Willy > >

[PATCH] improve travis-ci builds

2019-06-04 Thread Илья Шипицин
update LibreSSL to 2.9.2 speed up build by using "make -j3" cache BoringSSL checkout build prometeus exporter add basic cygwin build add USE_TFO=1, USE_SYSTEMD=1 to linux builds cheers, Ilya Shipitsin From ae71cc45c6db53b0ea4ce4361ecb6e367b75207b Mon Sep 17 00:00:00 2001

Re: cygwin build error

2019-06-04 Thread Илья Шипицин
вт, 4 июн. 2019 г. в 19:05, Willy Tarreau : > Hi Ilya, > > On Tue, Jun 04, 2019 at 12:52:50AM +0500, ??? wrote: > > src/mux_h2.o: In function `h2s_frt_make_resp_data': > > /home/chipitsine/haproxy/src/mux_h2.c:4405: undefined reference to > `trace' > >

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
e" resolved that > > cpp -v /dev/null -o /dev/null > > > > This should print the search path – we can then verify that /usr/include > and other dirs are in it. > > > > Bob > > > > *From:* Илья Шипицин > *Sent:* Monday, June 3, 2019 4:09 PM >

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
port-all-symbols > > endif > > > > # set the default settings according to the target above > > > > Other than these two rather small issues 2.0-dev5 built successfully on my > Cygwin (and I then also successfully built it with threading support, PCRE, > ZLib, Ope

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
must be missing in your build environment. > Most system headers should be in /usr/include if cygwin-devel is installed, > so you might want to start with checking if expected header files are there… > "something must be missing in your build environment" ... travis-ci is an ephemer

cygwin build error

2019-06-03 Thread Илья Шипицин
Hello, I'm trying yo build haproxy (git master) on cygwin. $ make CC=gcc V=1 TARGET=cygwin FLAGS= ... src/mux_h2.o: In function `h2s_frt_make_resp_data': /home/chipitsine/haproxy/src/mux_h2.c:4405: undefined reference to `trace' /home/chipitsine/haproxy/src/mux_h2.c:4405:(.text+0xce79):

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
> Regards, > > Gil > > On Mon, Jun 3, 2019 at 5:53 PM Илья Шипицин wrote: > >> >> >> пн, 3 июн. 2019 г. в 17:56, Willy Tarreau : >> >>> Hi Ilya, >>> >>> On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote: >>> >

Re: [ANNOUNCE] haproxy-2.0-dev5

2019-06-03 Thread Илья Шипицин
пн, 3 июн. 2019 г. в 16:56, Willy Tarreau : > Hi Aleks, > > On Mon, Jun 03, 2019 at 01:42:45PM +0200, Aleksandar Lazic wrote: > > Is this test usefull in docker setup? > > > > ## Starting vtest ## > > Testing with haproxy version: 2.0-dev5 > > #

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
пн, 3 июн. 2019 г. в 17:56, Willy Tarreau : > Hi Ilya, > > On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote: > > Hello, Gil Bahat! > > > > can you help with troubleshooting? > > > > I created some basic cygwin CI: > > > >

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
I forgot to notice - haproxy is very close to 2.0 release (about 2 weeks or so). we wish to be sure it works on cygwin before 2.0 released пн, 3 июн. 2019 г. в 13:57, Илья Шипицин : > Hello, Gil Bahat! > > can you help with troubleshooting? > > I created some basic cygwi

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
Hello, Gil Bahat! can you help with troubleshooting? I created some basic cygwin CI: https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L25-L30 it fails with src/ev_poll.c:16:10: fatal error: poll.h: No such file or directory #include ^~~~ compilation terminated.

Re: upcoming 2.0 release: freebsd-11 seem to be broken ?

2019-05-29 Thread Илья Шипицин
ср, 29 мая 2019 г. в 15:25, Dmitry Sivachenko : > > > > On 26 May 2019, at 23:40, Илья Шипицин wrote: > > > > Hello, > > > > I added freebsd-11 to cirrus-ci > > > > https://cirrus-ci.com/task/5162023978008576 > > > > should we fix it

Re: upcoming 2.0 release: freebsd-11 seem to be broken ?

2019-05-29 Thread Илья Шипицин
ср, 29 мая 2019 г. в 07:36, Willy Tarreau : > Hi Ilya, > > On Mon, May 27, 2019 at 01:40:42AM +0500, ??? wrote: > > Hello, > > > > I added freebsd-11 to cirrus-ci > > > > https://cirrus-ci.com/task/5162023978008576 > > > > should we fix it before 2.0 release ? > > As I mentioned on the

upcoming 2.0 release: freebsd-11 seem to be broken ?

2019-05-26 Thread Илья Шипицин
Hello, I added freebsd-11 to cirrus-ci https://cirrus-ci.com/task/5162023978008576 should we fix it before 2.0 release ? cheers, Ilya Shipitsin

Re: PATCH: memory leak fix

2019-05-25 Thread Илья Шипицин
I came with a better patch actually it is not required to free compression methods on OpenSSL >= 1.0.0 so, let us only do that when it is really neccessary сб, 25 мая 2019 г. в 14:59, Илья Шипицин : > hi, I see it it not yet applied. > it turned out that freeing breaks LibreSSL intern

Re: PATCH: memory leak fix

2019-05-25 Thread Илья Шипицин
hi, I see it it not yet applied. it turned out that freeing breaks LibreSSL internals. so, here's v2 (free only if not LibreSSL) сб, 25 мая 2019 г. в 10:46, Willy Tarreau : > Hi Ilya, > > > From 61f04a8ecdcfc105f732d5978180ad2ab746cc34 Mon Sep 17 00:00:00 2001 > > From: Ilya Shipitsin > >

PATCH: memory leak fix

2019-05-24 Thread Илья Шипицин
hello, memory leak was found by valgrind From 61f04a8ecdcfc105f732d5978180ad2ab746cc34 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Sat, 25 May 2019 03:38:14 +0500 Subject: [PATCH] BUG/MINOR: ssl_sock: Fix memory leak when disabling compression according to manpage:

Re: [ANNOUNCE] haproxy-2.0-dev4

2019-05-23 Thread Илья Шипицин
чт, 23 мая 2019 г. в 18:45, Willy Tarreau : > On Thu, May 23, 2019 at 04:17:33PM +0500, ??? wrote: > > I'd like to run sanitizers on vaious combinations, like ZLIB / SLZ, PCRE > / > > PCRE2 ... > > ok, let us do it before Wednesday > > OK, why not. Feel free to send patches once you can

Re: [ANNOUNCE] haproxy-2.0-dev4

2019-05-23 Thread Илья Шипицин
чт, 23 мая 2019 г. в 01:28, Willy Tarreau : > Hi, > > HAProxy 2.0-dev4 was released on 2019/05/22. It added 83 new commits > after version 2.0-dev3. > > This release completes the integration of a few pending features and > the ongoing necessary cleanups before 2.0. > > A few bugs were addressed

Re: cirrus-ci is red

2019-05-23 Thread Илья Шипицин
чт, 23 мая 2019 г. в 14:03, Willy Tarreau : > On Wed, May 22, 2019 at 07:15:21PM +0200, Willy Tarreau wrote: > > On Wed, May 22, 2019 at 03:24:25PM +0500, ??? wrote: > > > Hello, > > > > > > someone is reviewing this > https://github.com/haproxy/haproxy/runs/133866993 > > > ? > > > > So

do we consider using patchwork ?

2019-05-22 Thread Илья Шипицин
Hello, if we do not like using github PR and Willy receives 2k emails a day... do we consider using something like that https://patchwork.openvpn.net/project/openvpn2/list/ ? cheers, Ilya Shipitsin

Re: [PATCH v2] BUILD: add sanitizers to travis-ci builds

2019-05-22 Thread Илья Шипицин
done ср, 22 мая 2019 г. в 19:18, Willy Tarreau : > Hi Ilya, > > On Wed, May 22, 2019 at 06:37:58PM +0500, ??? wrote: > > build is green now, we can apply this patch (I skipped "linux-ppc64le" > for > > a while) > > It's really easier for me if you attach it again. I'm getting about 2k >

Re: [PATCH v2] BUILD: add sanitizers to travis-ci builds

2019-05-22 Thread Илья Шипицин
ср, 22 мая 2019 г. в 19:18, Willy Tarreau : > Hi Ilya, > > On Wed, May 22, 2019 at 06:37:58PM +0500, ??? wrote: > > build is green now, we can apply this patch (I skipped "linux-ppc64le" > for > > a while) > > It's really easier for me if you attach it again. I'm getting about 2k >

Re: [PATCH v2] BUILD: add sanitizers to travis-ci builds

2019-05-22 Thread Илья Шипицин
build is green now, we can apply this patch (I skipped "linux-ppc64le" for a while) ср, 22 мая 2019 г. в 18:37, : > From: Ilya Shipitsin > > full list of changes: > > use TARGET=osx instead of generic for osx builds, > add USE_PCRE_JIT=1, USE_GETADDRINFO=1 to build matrix, > enable address

cirrus-ci is red

2019-05-22 Thread Илья Шипицин
Hello, someone is reviewing this https://github.com/haproxy/haproxy/runs/133866993 ? thanks, Ilya Shipitcin

Re: [PATCH v2 1/1] BUG/MINOR: mworker: Fix memory leak of mworker_proc members

2019-05-22 Thread Илья Шипицин
more findings https://travis-ci.org/chipitsine/haproxy-1/jobs/535709949#L1938-L1948 ср, 22 мая 2019 г. в 15:12, Илья Шипицин : > here's build with patch applied > > https://travis-ci.org/chipitsine/haproxy-1/jobs/535709947#L604-L608 > > ср, 22 мая 2019 г. в 14:43, William Lall

  1   2   3   >