On Sat, Mar 21, 2020 at 01:18:48AM +0100, Moemen MHEDHBI wrote:
> Since we handle contributions via github pull requests (for tracking,
> referencing, searching purposes), I thought in the first place that we
> better avoid having same discussion scattered on different places.
You're right, that m
Hey Willy
On 20/03/2020 12:02, Willy Tarreau wrote:
> Hi Moemen,
>
> On Thu, Mar 19, 2020 at 06:47:42PM +0100, Moemen MHEDHBI wrote:
>> This ML is the right place to contribute to the HAProxy software, but
>> for the ingress controller better do this by creating an issue in the
>> github project.
Hello,
I played with "special purpose" job, which runs h2spec
here's code:
https://github.com/chipitsine/haproxy/commit/8c90ea82fd32c0ca9bd3df0ae7d9361525eda590
output:
https://github.com/chipitsine/haproxy/runs/522959386
I think such jobs might be run on schedule, for example weekly ?
che
Hi
I'd like to have better understanding how server-template and resolvers
work together. HAproxy 1.9.14.
Relevant sections from config:
resolvers dns
accepted_payload_size 1232
parse-resolv-conf
hold valid 90s
resolve_retries 3
timeout resolve 1s
timeout retry 1s
server-template
Hi Tim,
On 3/20/20 3:01 PM, Tim Düsterhus wrote:
> Emeric,
>
> Am 20.03.20 um 14:29 schrieb Emeric Brun:
>> So I understand that since 1.6 the SMP_T are directly announced on the wire
>> for key types, and it brokes the documented values and this is hazardous to
>> rely on internal enum values.
On Fri, Mar 20, 2020 at 03:12:46PM +0100, Emeric Brun wrote:
> I understood that documented values are:
> 0: signed integer
> 1: IPv4 address
> 2: IPv6 address
> 3: string
> 4: binary
>
> and currenty (since 1.6):
>2 = signed int
>4 = IPv4
>5 = IPv6
>6 = string
>7 = binary
Hi Willy,
On 3/20/20 2:53 PM, Willy Tarreau wrote:
> Hi Emeric,
>
> On Fri, Mar 20, 2020 at 02:29:48PM +0100, Emeric Brun wrote:
>> So I understand that since 1.6 the SMP_T are directly announced on the wire
>> for key types, and it brokes the documented values and this is hazardous to
>> rely on
I grabbed the source from the PPA and rebuilt it, installed the dbg
package, and here's one of the "bt full"s:
(gdb) bt full
#0 pattern_exec_match (head=head@entry=0x55e4dd275478,
smp=smp@entry=0x7fbf9ef650c0,
fill=fill@entry=0) at src/pattern.c:2541
__pl_l =
__pl_r =
li
Emeric,
Am 20.03.20 um 14:29 schrieb Emeric Brun:
> So I understand that since 1.6 the SMP_T are directly announced on the wire
> for key types, and it brokes the documented values and this is hazardous to
> rely on internal enum values.
>
> So we must re-introduce a mapping between internal an
On Fri, Mar 20, 2020 at 06:58:47PM +0500, ??? wrote:
> I admit that it looks like absurd. However, it works like a charm. There's
> pretty big and happy community around LogParser.
> Probably, I need to spend time to prepare example how that works.
>
> I used to use it heavily when workin
пт, 20 мар. 2020 г. в 18:49, Willy Tarreau :
> On Fri, Mar 20, 2020 at 06:06:47PM +0500, ??? wrote:
> > I am familiar with custom formats.
> > what I mean is (sample from IIS log)
> >
> > so I can query it like "select * from ... where sc-status=200" without
> > prior knowledge what fiel
Hi Emeric,
On Fri, Mar 20, 2020 at 02:29:48PM +0100, Emeric Brun wrote:
> So I understand that since 1.6 the SMP_T are directly announced on the wire
> for key types, and it brokes the documented values and this is hazardous to
> rely on internal enum values.
Yes that's the issue Tim spotted.
>
On Fri, Mar 20, 2020 at 06:06:47PM +0500, ??? wrote:
> I am familiar with custom formats.
> what I mean is (sample from IIS log)
>
> so I can query it like "select * from ... where sc-status=200" without
> prior knowledge what field "sc-status" is (format might change from file to
> file
On 20.03.20 14:06, Илья Шипицин wrote:
I am familiar with custom formats.
what I mean is (sample from IIS log)
so I can query it like "select * from ... where sc-status=200" without prior knowledge
what field "sc-status" is (format might change from file to file)
also, I guess log exporters
On 3/14/20 12:47 PM, Willy Tarreau wrote:
> On Sat, Mar 14, 2020 at 12:20:00PM +0100, Tim Düsterhus wrote:
>> Willy,
>>
>> Am 14.03.20 um 12:13 schrieb Willy Tarreau:
>>> Yes, feel free to do so, this will definitely help get it eventually done.
>>
>> Here it is: https://github.com/haproxy/haproxy/
I am familiar with custom formats.
what I mean is (sample from IIS log)
so I can query it like "select * from ... where sc-status=200" without
prior knowledge what field "sc-status" is (format might change from file to
file)
also, I guess log exporters may take advantage from it.
#Software: Mi
Hi.
On 20.03.20 13:15, Илья Шипицин wrote:
Hello,
there's Microsoft LogParser.
good thing about it, it likes self-consistent CSV logs (or TSV), when first
line is fields.
it helps to change log format on the fly (for example, in IIS), so IIS starts
new log once format is changed.
you can qu
Hello,
there's Microsoft LogParser.
good thing about it, it likes self-consistent CSV logs (or TSV), when first
line is fields.
it helps to change log format on the fly (for example, in IIS), so IIS
starts new log once format is changed.
you can query such logs without prior knowledge of fields,
Hi Moemen,
On Thu, Mar 19, 2020 at 06:47:42PM +0100, Moemen MHEDHBI wrote:
> This ML is the right place to contribute to the HAProxy software, but
> for the ingress controller better do this by creating an issue in the
> github project.
>
> It isn't your fault anyway, we have updated the contribu
oook.
I was about to add link to mailing list discussion and travis community
forum.
пт, 20 мар. 2020 г. в 15:57, Willy Tarreau :
> On Wed, Mar 18, 2020 at 11:58:09PM +0500, ??? wrote:
> > Hello,
> >
> > due to arm64 instability, let us disable arm64 builds until this is
> > resolv
On Wed, Mar 18, 2020 at 11:58:09PM +0500, ??? wrote:
> Hello,
>
> due to arm64 instability, let us disable arm64 builds until this is
> resolved.
And applied as well, thanks!
Willy
On Wed, Mar 18, 2020 at 09:29:27PM +0500, ??? wrote:
> Hello,
>
> to reduce build noise, let us skip PR builds
Merged, thanks Ilya.
Willy
On Wed, Mar 18, 2020 at 11:58:09PM +0500, Илья Шипицин wrote:
> Hello,
>
> due to arm64 instability, let us disable arm64 builds until this is
> resolved.
>
> Cheers,
> Ilya Shipitcin
> From b39b8a6e4ebcae5a28f497170d4ae8e6b208023f Mon Sep 17 00:00:00 2001
> From: Ilya Shipitsin
> Date: Wed, 18
On Thu, Mar 19, 2020 at 04:12:10PM +0100, Tim Duesterhus wrote:
> William,
>
> I hope I correctly understood the purpose of that `+ 1` there. The issue was
> found using a static analyzer that complained that `fcount` could be zero,
> leading to a 0 byte allocation. If this fix is incorrect then t
24 matches
Mail list logo
