stable-bot: NOTICE: 7 bug fixes in queue for next release - 1.8
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 to this mail must be sent to the mailing list. Last release 1.8.21 was issued on 2019/08/16. There are currently 7 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2019/08/23 - 3 MINOR, first one merged on 2019/08/23 Thus the computed ideal release date for 1.8.22 would be 2019/09/20, which is in three weeks or less. The current list of patches in the queue is: - MEDIUM : ssl: Use the early_data API the right way. - MEDIUM : checks: make sure the warmup task takes the server lock - MEDIUM : listener/threads: fix an AB/BA locking issue in delete_listener() - MEDIUM : spoe: Be sure the sample is found before setting its context - MINOR : logs/threads: properly split the log area upon startup - MINOR : haproxy: fix rule->file memory leak - MINOR : mworker: disable SIGPROF on re-exec --- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
stable-bot: NOTICE: 5 bug fixes in queue for next release - 2.0
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 to this mail must be sent to the mailing list. Last release 2.0.5 was issued on 2019/08/16. There are currently 5 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2019/08/23 - 1 MINOR, first one merged on 2019/08/26 Thus the computed ideal release date for 2.0.6 would be 2019/09/22, which is in three weeks or less. The current list of patches in the queue is: - MEDIUM : mux-h1: do not truncate trailing 0CRLF on buffer boundary - MEDIUM : url32 does not take the path part into account in the returned hash. - MEDIUM : listener/threads: fix an AB/BA locking issue in delete_listener() - MEDIUM : mux-h1: do not report errors on transfers ending on buffer full - MINOR : mworker: disable SIGPROF on re-exec --- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
stable-bot: WARNING: 6 bug fixes in queue for next release - 1.9
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 to this mail must be sent to the mailing list. Last release 1.9.10 was issued on 2019/08/08. There are currently 6 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2019/08/15 - 2 MINOR, first one merged on 2019/08/12 Thus the computed ideal release date for 1.9.11 would be 2019/09/09, which is in one week or less. The current list of patches in the queue is: - MEDIUM : mux-h1: do not truncate trailing 0CRLF on buffer boundary - MEDIUM : url32 does not take the path part into account in the returned hash. - MEDIUM : listener/threads: fix an AB/BA locking issue in delete_listener() - MEDIUM : lua: Fix test on the direction to set the channel exp timeout - MINOR : mworker: disable SIGPROF on re-exec - MINOR : lua: fix setting netfilter mark --- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
Hello
Who designed your website "formilux.org"??? Regards, Linda
Re: [PATCH] MINOR: send-proxy-v2: sends authority TLV according to TLV received
Hi Manu, On Thu, Aug 29, 2019 at 03:22:11PM +0200, Emmanuel Hocdet wrote: > This patch follows Geoff's patch. Thanks for this. I didn't remember we automatically copied the SNI into the PP. I'm suspecting that sooner or later we'll need a "set-authority" action to complete the set-dst and so-on. We'll see. Now merged, thanks, Willy
Re: HAProxy 2.0 "stick on src table mypeers/mytable" does not result in peers binding to socket address
Hi Bruno, On Sat, Aug 31, 2019 at 12:49:15AM +, Bruno Henc wrote: > Greetings, > > Using "stick on src table mypeers/stickysrc" in a backend results in HAProxy > deciding not to bind to the appropriate peers address for the local host > (i.e. HAProxy thinks there are no stick tables in use). However using a > http-request track-sc0 line will result in haproxy listening on the peers > address. Also, defining the stick table in the backend itself or in a dummy > backend also works. That's interesting. I suspect that the modifications to make the stick-table name resolution work recently overlooked the "stick" keyword. It's possible that it used to work differently from what was done later with the track-* keyword, since "stick" was the very first implementation of the stick tables. We'll see this with Fred on Monday. Thanks! Willy
