Hi Lukas,
On Mon, May 06, 2019 at 06:51:57PM +0200, Lukas Tribus wrote:
> There is room for improvement here. Can you confirm that attaching a
> patch file per commit to the email would fix this usability issue?
I'd say yes, provided the attachments are prefixed with a sequence
number, like
From: Ilya Shipitsin
Call missing scripts/build-ssl.sh (which actually builds SSL variants)
Enable OpenSSL, LibreSSL builds caching, it saves a bunch of time
LibreSSL builds are not allowed to fail anymore
Add openssl to osx builds
---
.travis.yml | 18 +++---
1 file changed, 7
Hello,
I built haproxy using gcc-9
make CC=gcc V=1 TARGET=linux2628 USE_ZLIB=1 USE_PCRE=1 USE_PCRE_JIT=1
USE_LUA=1 USE_OPENSSL=1 DEBUG_CFLAGS="-g -fsanitize=address"
LDFLAGS="-lasan"
finding is:
*** h10.1 debug|==8326==ERROR: LeakSanitizer: detected memory leaks
*** h10.1 debug|
***
From: Ilya Shipitsin
Added scripts/build-ssl.sh (without that script we were using openssl-1.0.2)
LibreSSL builds are not allowed to fail anymore
Enabled OpenSSL, LibreSSL build caching
Enabled openssl for osx builds
Ilya Shipitsin (1):
BUILD: travis-ci bugfixes and improvements
.travis.yml
On Sun, May 05, 2019 at 10:11:38PM +0200, Frederic Lecaille wrote:
> I had no access to any travis environment when it has been told in previous
> mails that /tmp could not work, and /var/tmp could not either.
> They were the first tested values.
>
> Now that I have setup a travis account, I have
there's some random failure
https://travis-ci.com/haproxy/haproxy/jobs/197824840
looks like test is not stable
пн, 6 мая 2019 г. в 11:11, Willy Tarreau :
> On Sun, May 05, 2019 at 10:11:38PM +0200, Frederic Lecaille wrote:
> > I had no access to any travis environment when it has been told in
Hi Alec,
On Tue, Apr 30, 2019 at 07:59:16PM +0800, Alec Liu wrote:
> > I'm seeing that you copied a doc retrieved from somewhere else that is
> > found at various places on the net. Have you checked the license for
> > this doc to be sure we can copy and distribute it like this ? It might
> > be
Hi.
Any answer to the questions below?
Regards
Aleks
Sat Apr 27 12:47:17 GMT+02:00 2019 Aleksandar Lazic :
> Hi.
>
>
> I have now created some HAProxy 2.0 images ;-).
>
> The outputs below raises some questions to me.
>
> * Should in the OPTIONS output also be the EXTRA_OBJS ?
> * Should
Hi Maciej,
On Mon, May 06, 2019 at 06:49:26AM +0200, Maciej Zdeb wrote:
> Hi,
>
> I confirm Willy patch fixed the problem! Thanks!
Great, thanks for confirming!
Willy
well, I hope travis-ci will be useful (or we will drop it).
as for PR, I meant that it should have been sent to list anyway (but it was
not sent for some reason).
I can send using "git send email" as well
пн, 6 мая 2019 г. в 11:05, Willy Tarreau :
> Hi Ilya,
>
> > I made another PR
> >
> >
On Mon, May 06, 2019 at 12:54:06PM +0500, ??? wrote:
> there's some random failure
>
> https://travis-ci.com/haproxy/haproxy/jobs/197824840
>
> looks like test is not stable
isn't it the same at the other one you reported that looked related to
the latest SSL fixes ?
Willy
Hi Ilya,
> I made another PR
>
> https://github.com/haproxy/haproxy/pull/92
Thank you.
> (I really like automatic PR to mailing list routing)
Well, it was the only workable workaround we have when people send PRs.
Sadly we can't block them. Apparently only mirror repositories can block
PRs
Hi Willy,
On Sun, May 05, 2019 at 07:07:21AM +0200, Willy Tarreau wrote:
> Hi William,
> > we got a similar issue with last v1.9.7+HEAD
> At first I thought you were again on a deadlock that I couldn't spot, due
> to the fact that nearly all threads were waiting on the LB lock, and I
> couldn't
Il 2019-04-18 18:33 Willy Tarreau ha scritto:
Hello Marco,
On Thu, Apr 18, 2019 at 05:27:26PM +0200, Marco Corte wrote:
Hello!
From time to time, about twice daily, and without any apparent reason,
haproxy jumps from using about 15% CPU usage to 100% (relative to the
single
core it can
On 5/6/19 9:54 AM, Илья Шипицин wrote:
there's some random failure
https://travis-ci.com/haproxy/haproxy/jobs/197824840
looks like test is not stable
According to the log, S13 and S37 syslog servers have the same port: 42464
Fred.
Hi,
is cygwin still supported anymore? the target seems to be present in the
Makefiles and I'd love to be able to use it. I'm running into what seems to
be a workable linker error:
$ make TARGET=cygwin
LD haproxy
src/http_act.o:http_act.c:(.rdata+0x340): multiple definition of
From: Apollon Oikonomopoulos
This will allow seamless upgrades from the sysvinit system while respecting
any changes the users may have made. It will also make local configuration
easier than overriding the systemd unit file.
Note by Tim:
This GPL-2 licensed patch was taken from the Debian
Unless the EXTRAOPTS variable is overriden in /etc/default/haproxy
the unit file will use the master socket by default.
This patch may be backported to 1.9 and depends on
MINOR: systemd: Use the variables from /etc/default/haproxy.
---
contrib/systemd/haproxy.service.in | 2 +-
1 file changed, 1
William,
Am 06.05.19 um 11:08 schrieb William Lallemand:
> This socket gives full admin access to HAProxy without being in the
> configuration, so it might surprise the user if it's there after an upgrade,
> it
> should really be configurable. But I agree that it could be nice to have it
> by
*From:* Tim Duesterhus [mailto:t...@bastelstu.be]
*Sent:* Monday, May 6, 2019, 07:00 EDT
*To:* haproxy@formilux.org
*Cc:* Apollon Oikonomopoulos ,
wlallem...@haproxy.com, w...@1wt.eu, ber...@debian.org, Tim Duesterhus
On Mon, May 06, 2019 at 01:08:35PM +0200, Tim Düsterhus wrote:
> List,
>
> I apologize for the stupid threading of the v2 patch. When I want to
> send a number of patches in-reply-to an existing thread: Should I put
> the --in-reply-to onto git format-patch or should I specify it in git
>
surprisingly, LibreSSL builds are green
пн, 6 мая 2019 г. в 13:03, Willy Tarreau :
> On Mon, May 06, 2019 at 12:54:06PM +0500, ??? wrote:
> > there's some random failure
> >
> > https://travis-ci.com/haproxy/haproxy/jobs/197824840
> >
> > looks like test is not stable
>
> isn't it
List,
I apologize for the stupid threading of the v2 patch. When I want to
send a number of patches in-reply-to an existing thread: Should I put
the --in-reply-to onto git format-patch or should I specify it in git
send-email?
This time I added it to git format-patch, but it did not make the
Tim,
On Mon, May 06, 2019 at 01:00:51PM +0200, Tim Duesterhus wrote:
> > Regarding the overriding of ExecStart, I disagree. In my opinion this is a
> > confusing solution for the user, when doing that the user won't have the
> > update
> > of the unit file in the package. Lots of people still
On Sun, May 05, 2019 at 03:06:31PM +0200, Tim Düsterhus wrote:
> William,
>
> Am 26.04.19 um 20:30 schrieb Tim Düsterhus:
> > William,
> >
> > Am 26.04.19 um 14:56 schrieb William Lallemand:
> >> On Fri, Apr 26, 2019 at 12:15:37AM +0200, Tim Duesterhus wrote:
> >>> [Service]
> >>>
On 5/6/19 11:25 AM, Frederic Lecaille wrote:
On 5/6/19 9:54 AM, Илья Шипицин wrote:
there's some random failure
https://travis-ci.com/haproxy/haproxy/jobs/197824840
looks like test is not stable
According to the log, S13 and S37 syslog servers have the same port: 42464
Obviously this is a
On Mon, May 06, 2019 at 07:15:11AM -0400, Patrick Hemmer wrote:
>
> /etc/default is a debianism. Other distros use different directories,
> such as RedHat which uses /etc/sysconfig
>
> -Patrick
Hi Patrick,
I don't think that's a problem, most distribution use their own unit file
anyway,
Hi Marcin,
On 5/6/19 3:15 PM, Marcin Deranek wrote:
> Hi Emeric,
>
> On 5/3/19 5:54 PM, Emeric Brun wrote:
>> Hi Marcin,
>>
>> On 5/3/19 4:56 PM, Marcin Deranek wrote:
>>> Hi Emeric,
>>>
>>> On 5/3/19 4:50 PM, Emeric Brun wrote:
>>>
I've a testing platform here but I don't use the usdm_drv
On Sun, May 05, 2019 at 09:40:02AM +0200, Willy Tarreau wrote:
> With this said, after studying the code a little bit more, I'm seeing a
> potential case where if we'd have a trailers entry in the HTX buffer but
> no end of message, we could loop forever there not consuming this block.
> I have no
Hi Ilya,
On Mon, May 06, 2019 at 12:54:56AM +0500, Илья Шипицин wrote:
> hello,
>
> when I first sent LibreSSL patches (it was 27th April 2019), reg-tests were
> ok.
> I suspect recent 0RTT patches could break LibreSSL things
>
> can someone have a look ?
>
>
❦ 6 mai 2019 13:46 +02, William Lallemand :
>> /etc/default is a debianism. Other distros use different directories,
>> such as RedHat which uses /etc/sysconfig
>>
>> -Patrick
>
> Hi Patrick,
>
> I don't think that's a problem, most distribution use their own unit file
> anyway, people should
On Mon, May 06, 2019 at 02:20:32PM +0200, Vincent Bernat wrote:
> However, many people prefer /etc/default and /etc/sysconfig to systemd
> overrides. And for distribution, it enables a smoother transition. For
> Debian, we would still add the EnvironmentFile directive. You could
> still be
Hi Marcin,
On 5/6/19 3:31 PM, Emeric Brun wrote:
> Hi Marcin,
>
> On 5/6/19 3:15 PM, Marcin Deranek wrote:
>> Hi Emeric,
>>
>> On 5/3/19 5:54 PM, Emeric Brun wrote:
>>> Hi Marcin,
>>>
>>> On 5/3/19 4:56 PM, Marcin Deranek wrote:
Hi Emeric,
On 5/3/19 4:50 PM, Emeric Brun wrote:
I have just noticed that "scripts/build-ssl.sh" is missing in .travis.yml
so, unfortunately, we are running all builds against xenial openssl-1.0.2
(no openssl-1.1.X, no libressl...)
I'm not sure when "scripts/build-ssl.sh" disappeared. I'll send new patch
soon
пн, 6 мая 2019 г. в 11:05, Willy
Hello Willy,
On Mon, 6 May 2019 at 08:06, Willy Tarreau wrote:
>
> Hi Ilya,
>
> > I made another PR
> >
> > https://github.com/haproxy/haproxy/pull/92
>
> Thank you.
>
> > (I really like automatic PR to mailing list routing)
>
> Well, it was the only workable workaround we have when people send
36 matches
Mail list logo
