stable-bot: Bugfixes waiting for a release 2.4 (1), 2.3 (2), 2.2 (1)

Hi, This is a friendly bot that watches fixes pending for the next haproxy-stable release! One such e-mail is sent periodically once patches are waiting in the last maintenance branch, and an ideal release date is computed based on the severity of these fixes and their merge date. Responses t

Re: [PATCH] variables cleanup/fixup

On Tue, Aug 31, 2021 at 06:37:45PM +0200, Willy Tarreau wrote: > > As such: Your patches LGTM, thanks. Please proceed :-) > > Will do, and reference the issue above and update the doc regarding ifexist, > just mentioning that it's now ignored for legacy compatibility. I'll finally wait for Christ

Re: [PATCH] variables cleanup/fixup

On Tue, Aug 31, 2021 at 04:41:16PM +0200, Tim Düsterhus wrote: > Willy, > > On 8/31/21 9:07 AM, Willy Tarreau wrote: > > I've finally implemented the replacement of the global variables table > > Okay, please refer to issue #624 in the commit: > https://github.com/haproxy/haproxy/issues/624. I be

Re: [PATCH] variables cleanup/fixup

Willy, On 8/31/21 9:07 AM, Willy Tarreau wrote: I've finally implemented the replacement of the global variables table Okay, please refer to issue #624 in the commit: https://github.com/haproxy/haproxy/issues/624. I believe it should be resolved afterwards. with a hash instead. However it

Bid Writing, Fundraising and Volunteering Workshops

NFP WORKSHOPS Affordable Training Courses Bid Writing Do you know the most common reasons for rejection? Are you gathering the right evidence? Are you making the right arguments? Are you using the right terminology? Are your numbers right? Are you learning from rejections? Are you ass

[PATCH] variables cleanup/fixup

Hi Tim, I've finally implemented the replacement of the global variables table with a hash instead. However it now obviously breaks the "ifexist" argument that you added to Lua's set_var() that was designed to work around the growing table problem. Given that the limitation used to be made on the