чт, 24 дек. 2020 г. в 07:53, Илья Шипицин :
>
>
> чт, 24 дек. 2020 г. в 01:51, Tim Düsterhus :
>
>> Ilya,
>>
>> Am 23.12.20 um 21:21 schrieb Илья Шипицин:
>> > this adds daily job.
>> > token specification also must be done, let us do it after merge.
>>
>> I've cleaned up the YML and commit
чт, 24 дек. 2020 г. в 01:51, Tim Düsterhus :
> Ilya,
>
> Am 23.12.20 um 21:21 schrieb Илья Шипицин:
> > this adds daily job.
> > token specification also must be done, let us do it after merge.
>
> I've cleaned up the YML and commit message a bit:
>
> a) Fixed some typos.
> b) Improved the naming
Hi Chad,
On Thu, Dec 24, 2020 at 2:46 PM Jonathan Opperman
wrote:
> Hi Chad,
>
> On Thu, Dec 24, 2020 at 2:04 PM Chad Lavoie wrote:
>
>> Greetings,
>>
>> On 12/23/2020 7:10 PM, Jonathan Opperman wrote:
>> >
>> > Works perfectly fine, what is the best way to hide /minio so it will
>> > rather
Hi Chad,
On Thu, Dec 24, 2020 at 2:04 PM Chad Lavoie wrote:
> Greetings,
>
> On 12/23/2020 7:10 PM, Jonathan Opperman wrote:
> >
> > Works perfectly fine, what is the best way to hide /minio so it will
> > rather say /storage so externally
> > I hide the fact that we are using minio?
>
> You
Greetings,
On 12/23/2020 7:10 PM, Jonathan Opperman wrote:
Works perfectly fine, what is the best way to hide /minio so it will
rather say /storage so externally
I hide the fact that we are using minio?
You can do that by using 'http-request set-path
%[regsub(^/storage,/minio)]' to
Hi All,
Wanted to get some advice if this is even possible? Want to route
https://www.portal.example/minio to a minio instance in the backend.
Running haproxy 1.8
configured an acl
acl PATH_minio path_beg -i /minio
then using backend:
use_backend bk_minio_portal if portal PATH_minio
backend
Ilya,
Am 23.12.20 um 21:21 schrieb Илья Шипицин:
> this adds daily job.
> token specification also must be done, let us do it after merge.
I've cleaned up the YML and commit message a bit:
a) Fixed some typos.
b) Improved the naming of the Workflow and the workflow steps.
c) Add newlines to
Hello,
this adds daily job.
token specification also must be done, let us do it after merge.
Ilya
From 6f52831ee614a334ac5b8ab2c2b29d5e51a681d2 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 24 Dec 2020 01:18:04 +0500
Subject: [PATCH] CI: Github ACtions: enable daily Coverity scan
Dear list,
on http://www.haproxy.org/ :
> We always support at least two active versions in parallel and an extra
> old one in critical fixes mode only. The currently supported versions
> are :
Then, all releases to 1.5 are listed. I think we don't support 1.5
anymore :)
Could someone fix the
On Wed, Dec 23, 2020 at 03:12:38PM +0100, Ionel GARDAIS wrote:
> My bad, I wasn't up to date.
No worries, a devel version is never up to date by definition!
> Olivier's fix is OK : no more CPU hogging.
Perfect, thanks for the quick test!
Willy
My bad, I wasn't up to date.
Olivier's fix is OK : no more CPU hogging.
--
Ionel
- Mail original -
De: "Willy Tarreau"
À: "Ionel GARDAIS"
Cc: "David CARLIER" , "haproxy"
Envoyé: Mercredi 23 Décembre 2020 14:52:32
Objet: Re: [*EXT*] Re: Quick question on atomics on ARM
On Wed, Dec
On Wed, Dec 23, 2020 at 02:48:17PM +0100, Ionel GARDAIS wrote:
> For what it's worth, I tried to build haproxy on Apple M1.
> It builds OK but at run, it's stuck in the initial pool_flush, hogging 100%
> CPU.
>
> the assembly part of __ha_cas_dw for __aarch64__ seems to be ignored.
What version
For what it's worth, I tried to build haproxy on Apple M1.
It builds OK but at run, it's stuck in the initial pool_flush, hogging 100% CPU.
the assembly part of __ha_cas_dw for __aarch64__ seems to be ignored.
--
Ionel
- Mail original -
De: "Willy Tarreau"
À: "David CARLIER"
Cc:
13 matches
Mail list logo
