Re: some updates around haproxy-dconv

[Willy Tarreau]

Hi Cyril,

On Sun, Oct 16, 2022 at 08:49:48PM +0200, Cyril Bonté wrote:
> Hi all !
> 
> Yes, I'm quite far from the mailing list, and I fear I won't be as active as
> before for some more times.

life happens...

> Nevertheless, here are some updates :
> 
> * Concerning the syntax for keywords with undelimited arguments (containing
> "..."), I've just left a comment here :
> https://github.com/haproxy/haproxy/pull/1888#issuecomment-1280026631

That's probably something we can adjust in the doc for the time being,
before we find a more robust solution.

> * About unordered chapters, I've also committed a fix.
> https://github.com/haproxy/haproxy/issues/996#issuecomment-1280024320

Thanks!

> * When it started, https://docs.haproxy.org/ was experimental and we decided
> not to remove docs in https://cbonte.github.io/haproxy-dconv/. It seems it
> is now mature and is the official place for the documentation. If you're OK
> with that, I'll remove the docs on the github side to redirect user to
> haproxy.org.

Sounds good indeed, thank you!

> * I've also noticed that the quick reference on docker hub still references
> https://cbonte.github.io/haproxy-dconv/. I'm not sure about who maintains
> this page but it may be a good idea to update to haproxy.org.
> See https://hub.docker.com/_/haproxy

According to the wiki it's maintained by docker, but I seem to remember
that Tim contributes to it. Anyway, do not underestimate the longevity
of links sprayed everywhere on the net, that one will probably continue
to receive traffic for another decade ;-)

Thanks,
Willy

Re: [PATCH] improve quictls build time

[Willy Tarreau]

On Sat, Oct 15, 2022 at 10:10:38AM +0500,  ??? wrote:
> Hello,
> 
> currently QuicTLS takes 3m40s
> disabling "tests" saves 40sec per build.

Applied, thank you Ilya!
Willy

Blocking IO in "lua tasks"

[Abhijeet Rastogi]

Hi HAproxy community,

I've already read through API Docs and lua.txt on the Github repo, but I
still have questions about implementing Lua tasks with blocking IO.

Facts from my reading:-
* "Lua tasks" do run in *"runtime mode"*
* They are *concurrent with HTTP traffic processing.*
* "core.thread = 0" so the Lua state is shared with all threads.

Logically thinking without knowing implementation details, it makes sense
that blocking IO shouldn't be part of "fetches/actions, etc", but it feels
like that shouldn't be true for "background tasks" as it is mentioned that
they run in separate threads.

Is updating ACLs by doing disk IO via background tasks an acceptable way of
doing that at scale? This example

was
linked on the arpalert.org website but it seems to use *"io.* methods in
runtime"*.

Cheers,
Abhijeet (https://abhi.host)

some updates around haproxy-dconv

[Cyril Bonté]

Hi all !

Yes, I'm quite far from the mailing list, and I fear I won't be as 
active as before for some more times.


Nevertheless, here are some updates :

* Concerning the syntax for keywords with undelimited arguments 
(containing "..."), I've just left a comment here :

https://github.com/haproxy/haproxy/pull/1888#issuecomment-1280026631

* About unordered chapters, I've also committed a fix.
https://github.com/haproxy/haproxy/issues/996#issuecomment-1280024320

* When it started, https://docs.haproxy.org/ was experimental and we 
decided not to remove docs in https://cbonte.github.io/haproxy-dconv/. 
It seems it is now mature and is the official place for the 
documentation. If you're OK with that, I'll remove the docs on the 
github side to redirect user to haproxy.org.


* I've also noticed that the quick reference on docker hub still 
references https://cbonte.github.io/haproxy-dconv/. I'm not sure about 
who maintains this page but it may be a good idea to update to haproxy.org.

See https://hub.docker.com/_/haproxy

Thanks ;)
Cyril Bonté