пт, 8 мая 2020 г. в 11:35, Martin Grigorov :
> Hi,
>
> I think I understand why it started failing.
> It must have started failing when you updated the version of OpenSSL.
> .travis.yml caches ~/opt folder between builds. After the update to 1.1.1f
> the build doesn't see the OpenSSL binaries in t
пт, 8 мая 2020 г. в 11:27, Willy Tarreau :
> On Fri, May 08, 2020 at 11:12:00AM +0500, ??? wrote:
> > btw, in my fork it is green
> > https://travis-ci.com/github/chipitsine/haproxy/jobs/329528056
>
> Cool, that tends to confirm the issue remains a bit random. There
> is actually somethin
Hi,
I think I understand why it started failing.
It must have started failing when you updated the version of OpenSSL.
.travis.yml caches ~/opt folder between builds. After the update to 1.1.1f
the build doesn't see the OpenSSL binaries in the cache anymore and tries
to download it and build it.
B
On Fri, May 08, 2020 at 11:12:00AM +0500, ??? wrote:
> btw, in my fork it is green
> https://travis-ci.com/github/chipitsine/haproxy/jobs/329528056
Cool, that tends to confirm the issue remains a bit random. There
is actually something I don't like in the build report, which is
that the "
Hi Martin,
On Fri, May 08, 2020 at 08:56:07AM +0300, Martin Grigorov wrote:
> Unfortunately it is not good:
> https://travis-ci.com/github/haproxy/haproxy/jobs/329657180
Indeed it's still not fixed on Travis' side. However what Ilya did
actually worked, in that the status is not reported as a glo
пт, 8 мая 2020 г. в 10:56, Martin Grigorov :
> Hi all,
>
> On Thu, May 7, 2020 at 11:56 PM Willy Tarreau wrote:
>
>> Hi Ilya,
>>
>> On Thu, May 07, 2020 at 09:19:48PM +0500, ??? wrote:
>> > Hello,
>> >
>> > let us enable arm64 builds back.
>>
>> Good idea, just merged now. Let's see how
Hi all,
On Thu, May 7, 2020 at 11:56 PM Willy Tarreau wrote:
> Hi Ilya,
>
> On Thu, May 07, 2020 at 09:19:48PM +0500, ??? wrote:
> > Hello,
> >
> > let us enable arm64 builds back.
>
> Good idea, just merged now. Let's see how that ends up now.
>
Unfortunately it is not good:
https://t
Hi Ilya,
On Thu, May 07, 2020 at 09:19:48PM +0500, ??? wrote:
> Hello,
>
> let us enable arm64 builds back.
Good idea, just merged now. Let's see how that ends up now.
Thanks,
Willy
Patrick,
On Thu, May 07, 2020 at 07:42:49PM +0200, Tim Düsterhus wrote:
> >> Please note that I review patches on a voluntary basis. I'm not an
> >> "employed first level reviewer".
> >
> > That's not what I meant. I thought that when regular participants on
> > this list do not spot the errors o
Patrick,
Am 07.05.20 um 18:54 schrieb Patrick Gansterer:
>> I skipped the patch (that's why I did not ACK the first, but only the
>> second one), because it was a very large change of code that was just
>> moved. Nonetheless I should have noticed the missing body and noted that
>> during my review
I,m interesting guest post..
can you published my article with link on your site
https://www.haproxy.org/
we need Dofollow link ..
we need Permanent post
Payment method PayPal
please reply me as soon as possible
thanks..
On 07.05.20 18:23, Tim Düsterhus wrote:> This is about your "[PATCH 1/2]
MINOR: crypto: Move aes_gcm_dec
implementation into new file". It does not contain a body, but instead
just a subject.
Ok, agree.
I skipped the patch (that's why I did not ACK the first, but only the
second one), because
Patrick,
Am 07.05.20 um 18:04 schrieb Patrick Gansterer:
> On 07.05.20 17:35, Willy Tarreau wrote:
>> Indeed. I encourage to ping again after one week because usually when you
>> restart with a new week of work, the previous one is definitely in old
>> history and will only be revisited by pure lu
Hello,
let us enable arm64 builds back.
Cheers,
Ilya Shipitcin
From 8c68b4494ba37469de86798fd7c492e38a2a8668 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 7 May 2020 20:57:26 +0500
Subject: [PATCH] CI: travis-ci: enable arm64 builds again
travis-ci arm64 were temporarily disabled du
On 07.05.20 17:35, Willy Tarreau wrote:
Indeed. I encourage to ping again after one week because usually when you
restart with a new week of work, the previous one is definitely in old
history and will only be revisited by pure luck.
I don't want to look impatient, so I waited 2 weeks. ;-)
Wi
On Thu, May 07, 2020 at 04:48:50PM +0200, Christopher Faulet wrote:
> Le 07/05/2020 à 13:03, Patrick Gansterer a écrit :
> > Hi,
> >
> > On 22.04.20 18:30, Tim Düsterhus wrote:
> > > I don't find anything to complain about now. I'll now leave it up to the
> > > authority to either apply or complai
Le 07/05/2020 à 16:48, Christopher Faulet a écrit :
Le 07/05/2020 à 13:03, Patrick Gansterer a écrit :
Hi,
On 22.04.20 18:30, Tim Düsterhus wrote:
I don't find anything to complain about now. I'll now leave it up to the
authority to either apply or complain.
How long does it usually take to
Le 07/05/2020 à 13:03, Patrick Gansterer a écrit :
Hi,
On 22.04.20 18:30, Tim Düsterhus wrote:
I don't find anything to complain about now. I'll now leave it up to the
authority to either apply or complain.
How long does it usually take to get a response?
I posted a similar patch already 2 y
Le 07/05/2020 à 15:27, Adis Nezirovic a écrit :
On 5/7/20 2:44 PM, William Lallemand wrote:
On Thu, May 07, 2020 at 02:39:30PM +0200, Christopher Faulet wrote:
Sorry for the delay and thanks for the reminder. I don't really know how stick
table works internally. But you should probably test the
On 5/7/20 2:44 PM, William Lallemand wrote:
On Thu, May 07, 2020 at 02:39:30PM +0200, Christopher Faulet wrote:
Sorry for the delay and thanks for the reminder. I don't really know how stick
table works internally. But you should probably test the dict_entry pointer is
not NULL before accessing
On Thu, May 07, 2020 at 02:39:30PM +0200, Christopher Faulet wrote:
> Le 07/05/2020 à 12:17, Adis Nezirovic a écrit :
> > Hello guys, any comments on the patch?
> >
> > Bump, adding Thierry to the conversation.
> >
> >
> > Best regards,
> >
>
> Hi Adis,
>
> Sorry for the delay and thanks for
Le 07/05/2020 à 12:17, Adis Nezirovic a écrit :
Hello guys, any comments on the patch?
Bump, adding Thierry to the conversation.
Best regards,
Hi Adis,
Sorry for the delay and thanks for the reminder. I don't really know how stick
table works internally. But you should probably test the d
Patrick,
Am 07.05.20 um 13:03 schrieb Patrick Gansterer:
> Hi,
>
> On 22.04.20 18:30, Tim Düsterhus wrote:
>> I don't find anything to complain about now. I'll now leave it up to the
>> authority to either apply or complain.
>
> How long does it usually take to get a response?
Usually not this
Hi,
On 22.04.20 18:30, Tim Düsterhus wrote:
I don't find anything to complain about now. I'll now leave it up to the
authority to either apply or complain.
How long does it usually take to get a response?
I posted a similar patch already 2 years ago and never got a response
from the maintain
Hello haproxy.org team,
I'm a representative of the Profy1 outreach marketing team. Our company
would like to cooperate with you.
We are interested in publishing a guest/sponsored article with a permanent
do-follow link indexed by Google on your site.
We have different topics and would like to p
Hello guys, any comments on the patch?
Bump, adding Thierry to the conversation.
Best regards,
--
Adis Nezirovic
Software Engineer
HAProxy Technologies - Powering your uptime!
375 Totten Pond Road, Suite 302 | Waltham, MA 02451, US
+1 (844) 222-4340 | https://www.haproxy.com
On Thu, May 07, 2020 at 10:20:15AM +0200, Remi Gacogne wrote:
> Hello,
>
> On 5/7/20 12:01 AM, Lukas Tribus wrote:
> >> I'm fine with that, most people use at least a value of 2048 because of
> >> the warning, their modern distribution will probably deny a lower value,
> >> and we add this warning
Hello,
On 5/7/20 12:01 AM, Lukas Tribus wrote:
>> I'm fine with that, most people use at least a value of 2048 because of
>> the warning, their modern distribution will probably deny a lower value,
>> and we add this warning a long time ago.
>
> I agree, we should default to 2048 and remove warni
Hi Christopher.
On 07.05.20 07:55, Christopher Faulet wrote:
> Le 07/05/2020 à 00:06, Aleksandar Lazic a écrit :
>> On 07.05.20 00:02, Lukas Tribus wrote:
>>> On Wed, 6 May 2020 at 23:33, Aleksandar Lazic wrote:
Hi.
The doc for [tcp|http]-check expect have some *-status argume
29 matches
Mail list logo
