Re: Deadlock lua when calling register_task inside action function

Hi, Thanks for the fast fix, everything works fine now! Cheers, Flakebi On Sun, 6 Jan 2019 19:11:21 +0100 Thierry Fournier wrote: > Hi, > > Thanks for the bug report. > Your "uneducated guess" was right. > > Could you test the patch in attachment ? > > Thanks > Thierry pgp3vWrqoKOPK.pgp D

[PATCH] Re: Question re lua and tcp content

Hi, Thanks fir the bug report. It is fixed by attached patch. Willy, could you merge this patch ? Thanks, Thierry 0001-BUG-MINOR-bad-args-are-returned-for-Lua-actions.patch Description: Binary data > On 31 Dec 2018, at 18:53, FRANKS, Andy (SHREWSBURY AND TELFORD HOSPITAL NHS > TRUST) wrot

Re: Deadlock lua when calling register_task inside action function

Hi, Thanks for the bug report. Your "uneducated guess" was right. Could you test the patch in attachment ? Thanks Thierry 0001-BUG-MEDIUM-dead-lock-when-Lua-tasks-are-trigerred.patch Description: Binary data > On 2 Jan 2019, at 01:40, Flakebi wrote: > > Hi, > > I am currently trying to se

Re: haproxy issue tracker discussion

Ansible, for example (https://github.com/ansible/ansible/issues), uses some advanced automation and templates to manage their enormous issues stream. Issue are checked against conforming rules/tests/codestyle checks or, for example, automatically closed due inactivity I believe most if not all solu

haproxy issue tracker discussion

Hello everyone, as per Tim's suggestion I'm restarting the discussion about the issue tracker, started in "haproxy 1.9 status update" (2018-05-25), Message-ID 20180525161044.ga6...@1wt.eu: https://www.mail-archive.com/haproxy@formilux.org/msg30139.html > It would be nice to show what's pending

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

Hi, 2 weeks passed without reply, so a little hereby a little 'bump'.. I know everyone has been busy, but would be nice to get test added or at least the biggest issue of the 'mailbomb' fixed before next release. If its 'scheduled' to get looked at later thats okay. Just making sure it aint fo

compression in defaults happens twice with 1.9.0

Hi List, Using both 1.9.0 and 2.0-dev0-909b9d8 compression happens twice when configured in defaults. This was noticed by user walle303 on IRC. Seems like a bug to me as 1.8.14 does not show this behavior. Attached a little regtest that reproduces the issue. Can someone take a look, thanks