stable-bot: Bugfixes waiting for a release 2.4 (23), 2.3 (11), 2.2 (5), 2.0 (5)
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.4.4 was issued on 2021-09-07. There are currently 23 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2021-09-20 - 4 MEDIUM, first one merged on 2021-09-10 - 18 MINOR, first one merged on 2021-09-08 Thus the computed ideal release date for 2.4.5 would be 2021-10-04, which is in one week or less. Last release 2.3.14 was issued on 2021-09-07. There are currently 11 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-09-20 - 9 MINOR, first one merged on 2021-09-20 Thus the computed ideal release date for 2.3.15 would be 2021-10-18, which is in three weeks or less. Last release 2.2.17 was issued on 2021-09-07. There are currently 5 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-09-20 - 4 MINOR, first one merged on 2021-09-20 Thus the computed ideal release date for 2.2.18 would be 2021-11-15, which is in seven weeks or less. Last release 2.0.25 was issued on 2021-09-07. There are currently 5 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-09-20 - 4 MINOR, first one merged on 2021-09-20 Thus the computed ideal release date for 2.0.26 would be 2021-12-13, which is in eleven weeks or less. The current list of patches in the queue is: - 2.4 - MAJOR : mux-h1: Don't eval input data if an error was reported - 2.4 - MEDIUM : mux-h1: Remove "Upgrade:" header for requests with payload - 2.0 - MEDIUM : http: check for a channel pending data before waiting - 2.4 - MEDIUM : leastconn: fix rare possibility of divide by zero - 2.2, 2.3, 2.4 - MEDIUM : stream-int: Don't block SI on a channel policy if EOI is reached - 2.3, 2.4 - MEDIUM : http-ana: Reset channels analysers when returning an error - 2.4 - MINOR : vars: improve accuracy of the rules used to check expression validity - 2.4 - MINOR : vars: truncate the variable name in error reports about scope. - 2.0, 2.2, 2.3, 2.4- MINOR : cli/payload: do not search for args inside payload - 2.4 - MINOR : vars: properly set the argument parsing context in the expression - 2.2, 2.3, 2.4 - MINOR : tcpcheck: Improve LDAP response parsing to fix LDAP check - 2.3, 2.4 - MINOR : lua: Don't yield in channel.append() and channel.set() - 2.3, 2.4 - MINOR : filters: Always set FLT_END analyser when CF_FLT_ANALYZE flag is set - 2.3, 2.4 - MINOR : lua: Yield in channel functions only if lua context can yield - 2.3, 2.4 - MINOR : filters: Set right FLT_END analyser depending on channel - 2.4 - MINOR : connection: prevent null deref on mux cleanup task allocation - 2.0, 2.2, 2.3, 2.4- MINOR : systemd: ExecStartPre must use -Ws - 2.0, 2.2, 2.3, 2.4- MINOR : compat: make sure __WORDSIZE is always defined - 2.4 - MINOR : server: allow 'enable health' only if check configured - 2.3, 2.4 - MINOR : stream: Don't release a stream if FLT_END is still registered - 2.4 - MINOR : flt-trace: fix an infinite loop when random-parsing is set - 2.0 - MINOR : stats: fix the POST requests processing in legacy mode - 2.4 - MINOR : h1-htx: Fix a typo when request parser is reset - 2.4 - MINOR : http-ana: increment internal_errors counter on response error - 2.4 - MINOR : vars: do not talk about global section in CLI errors for set-var -- 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: Bugfixes waiting for a release 2.4 (15), 2.3 (11), 2.2 (5), 2.0 (5)
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.4.4 was issued on 2021-09-07. There are currently 15 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2021-09-20 - 3 MEDIUM, first one merged on 2021-09-10 - 11 MINOR, first one merged on 2021-09-08 Thus the computed ideal release date for 2.4.5 would be 2021-10-04, which is in two weeks or less. Last release 2.3.14 was issued on 2021-09-07. There are currently 11 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-09-20 - 9 MINOR, first one merged on 2021-09-20 Thus the computed ideal release date for 2.3.15 would be 2021-10-18, which is in four weeks or less. Last release 2.2.17 was issued on 2021-09-07. There are currently 5 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-09-20 - 4 MINOR, first one merged on 2021-09-20 Thus the computed ideal release date for 2.2.18 would be 2021-11-15, which is in eight weeks or less. Last release 2.0.25 was issued on 2021-09-07. There are currently 5 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-09-20 - 4 MINOR, first one merged on 2021-09-20 Thus the computed ideal release date for 2.0.26 would be 2021-12-13, which is in twelve weeks or less. The current list of patches in the queue is: - 2.4 - MAJOR : mux-h1: Don't eval input data if an error was reported - 2.3, 2.4 - MEDIUM : http-ana: Reset channels analysers when returning an error - 2.4 - MEDIUM : mux-h1: Remove "Upgrade:" header for requests with payload - 2.2, 2.3, 2.4 - MEDIUM : stream-int: Don't block SI on a channel policy if EOI is reached - 2.0 - MEDIUM : http: check for a channel pending data before waiting - 2.0 - MINOR : stats: fix the POST requests processing in legacy mode - 2.4 - MINOR : flt-trace: fix an infinite loop when random-parsing is set - 2.4 - MINOR : connection: prevent null deref on mux cleanup task allocation - 2.0, 2.2, 2.3, 2.4- MINOR : cli/payload: do not search for args inside payload - 2.3, 2.4 - MINOR : lua: Yield in channel functions only if lua context can yield - 2.3, 2.4 - MINOR : stream: Don't release a stream if FLT_END is still registered - 2.0, 2.2, 2.3, 2.4- MINOR : systemd: ExecStartPre must use -Ws - 2.3, 2.4 - MINOR : filters: Always set FLT_END analyser when CF_FLT_ANALYZE flag is set - 2.3, 2.4 - MINOR : lua: Don't yield in channel.append() and channel.set() - 2.0, 2.2, 2.3, 2.4- MINOR : compat: make sure __WORDSIZE is always defined - 2.3, 2.4 - MINOR : filters: Set right FLT_END analyser depending on channel - 2.2, 2.3, 2.4 - MINOR : tcpcheck: Improve LDAP response parsing to fix LDAP check -- 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: 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 to this mail must be sent to the mailing list. Last release 2.4.3 was issued on 2021-08-17. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-08-20 Thus the computed ideal release date for 2.4.4 would be 2021-09-19, which is in three weeks or less. Last release 2.3.13 was issued on 2021-08-17. There are currently 2 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-08-20 Thus the computed ideal release date for 2.3.14 would be 2021-09-19, which is in three weeks or less. Last release 2.2.16 was issued on 2021-08-17. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-08-20 Thus the computed ideal release date for 2.2.17 would be 2021-10-19, which is in seven weeks or less. The current list of patches in the queue is: - 2.3 - MEDIUM : sock: really fix detection of early connection failures in for 2.3- - 2.2, 2.3, 2.4 - MEDIUM : h2: match absolute-path not path-absolute for :path -- 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: Bugfixes waiting for a release 2.4 (1), 2.3 (1), 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 to this mail must be sent to the mailing list. Last release 2.4.3 was issued on 2021-08-17. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-08-20 Thus the computed ideal release date for 2.4.4 would be 2021-09-19, which is in four weeks or less. Last release 2.3.13 was issued on 2021-08-17. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-08-20 Thus the computed ideal release date for 2.3.14 would be 2021-09-19, which is in four weeks or less. Last release 2.2.16 was issued on 2021-08-17. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-08-20 Thus the computed ideal release date for 2.2.17 would be 2021-10-19, which is in eight weeks or less. The current list of patches in the queue is: - 2.2, 2.3, 2.4 - MEDIUM : h2: match absolute-path not path-absolute for :path -- 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: Bugfixes waiting for a release 2.4 (11), 2.3 (7), 2.0 (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 to this mail must be sent to the mailing list. Last release 2.4.2 was issued on 2021-07-07. There are currently 11 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-07-27 - 9 MINOR, first one merged on 2021-07-15 Thus the computed ideal release date for 2.4.3 would be 2021-08-12, which was within the last week. Last release 2.3.12 was issued on 2021-07-08. There are currently 7 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-07-27 - 5 MINOR, first one merged on 2021-07-27 Thus the computed ideal release date for 2.3.13 would be 2021-08-24, which is in two weeks or less. Last release 2.0.23 was issued on 2021-07-16. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-07-29 Thus the computed ideal release date for 2.0.24 would be 2021-10-27, which is in eleven weeks or less. The current list of patches in the queue is: - 2.0 - MEDIUM : tcp-check: Do not dereference inexisting connection - 2.3, 2.4 - MEDIUM : ssl_sample: fix segfault for srv samples on invalid request - 2.3, 2.4 - MEDIUM : mworker: do not register an exit handler if exit is expected - 2.4 - MINOR : ssl: Default-server configuration ignored by server - 2.4 - MINOR : mux-h1: Be sure to swap H1C to splice mode when rcv_pipe() is called - 2.3, 2.4 - MINOR : systemd: must check the configuration using -Ws - 2.3, 2.4 - MINOR : check: fix the condition to validate a port-less server - 2.3, 2.4 - MINOR : resolvers: Use a null-terminated string to lookup in servers tree - 2.3, 2.4 - MINOR : mux-h2: Obey dontlognull option during the preface - 2.4 - MINOR : stats: Add missing agent stats on servers - 2.4 - MINOR : mux-h1: Obey dontlognull option for empty requests - 2.3, 2.4 - MINOR : mworker: do not export HAPROXY_MWORKER_REEXEC across programs -- 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: Bugfixes waiting for a release 2.4 (11), 2.3 (7), 2.0 (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 to this mail must be sent to the mailing list. Last release 2.4.2 was issued on 2021-07-07. There are currently 11 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-07-27 - 9 MINOR, first one merged on 2021-07-15 Thus the computed ideal release date for 2.4.3 would be 2021-08-12, which is in one week or less. Last release 2.3.12 was issued on 2021-07-08. There are currently 7 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-07-27 - 5 MINOR, first one merged on 2021-07-27 Thus the computed ideal release date for 2.3.13 would be 2021-08-24, which is in three weeks or less. Last release 2.0.23 was issued on 2021-07-16. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2021-07-29 Thus the computed ideal release date for 2.0.24 would be 2021-10-27, which is in twelve weeks or less. The current list of patches in the queue is: - 2.3, 2.4 - MEDIUM : ssl_sample: fix segfault for srv samples on invalid request - 2.0 - MEDIUM : tcp-check: Do not dereference inexisting connection - 2.3, 2.4 - MEDIUM : mworker: do not register an exit handler if exit is expected - 2.4 - MINOR : mux-h1: Be sure to swap H1C to splice mode when rcv_pipe() is called - 2.4 - MINOR : mux-h1: Obey dontlognull option for empty requests - 2.3, 2.4 - MINOR : check: fix the condition to validate a port-less server - 2.3, 2.4 - MINOR : resolvers: Use a null-terminated string to lookup in servers tree - 2.3, 2.4 - MINOR : mux-h2: Obey dontlognull option during the preface - 2.4 - MINOR : ssl: Default-server configuration ignored by server - 2.4 - MINOR : stats: Add missing agent stats on servers - 2.3, 2.4 - MINOR : systemd: must check the configuration using -Ws - 2.3, 2.4 - MINOR : mworker: do not export HAPROXY_MWORKER_REEXEC across programs -- 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: Bugfixes waiting for a release 2.4 (11), 2.3 (7)
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.4.2 was issued on 2021-07-07. There are currently 11 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-07-27 - 9 MINOR, first one merged on 2021-07-15 Thus the computed ideal release date for 2.4.3 would be 2021-08-12, which is in two weeks or less. Last release 2.3.12 was issued on 2021-07-08. There are currently 7 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2021-07-27 - 5 MINOR, first one merged on 2021-07-27 Thus the computed ideal release date for 2.3.13 would be 2021-08-24, which is in four weeks or less. The current list of patches in the queue is: - 2.3, 2.4 - MEDIUM : mworker: do not register an exit handler if exit is expected - 2.3, 2.4 - MEDIUM : ssl_sample: fix segfault for srv samples on invalid request - 2.4 - MINOR : mux-h1: Be sure to swap H1C to splice mode when rcv_pipe() is called - 2.3, 2.4 - MINOR : resolvers: Use a null-terminated string to lookup in servers tree - 2.3, 2.4 - MINOR : mux-h2: Obey dontlognull option during the preface - 2.3, 2.4 - MINOR : mworker: do not export HAPROXY_MWORKER_REEXEC across programs - 2.3, 2.4 - MINOR : systemd: must check the configuration using -Ws - 2.4 - MINOR : ssl: Default-server configuration ignored by server - 2.4 - MINOR : stats: Add missing agent stats on servers - 2.3, 2.4 - MINOR : check: fix the condition to validate a port-less server - 2.4 - MINOR : mux-h1: Obey dontlognull option for empty requests -- 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: Bugfixes waiting for a release 2.4 (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 to this mail must be sent to the mailing list. Last release 2.4.2 was issued on 2021-07-07. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2021-07-15 Thus the computed ideal release date for 2.4.3 would be 2021-08-12, which is in three weeks or less. The current list of patches in the queue is: - 2.4 - MINOR : ssl: Default-server configuration ignored by server -- 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: Bugfixes waiting for a release 2.3 (10), 2.1 (44), 2.0 (26)
- MINOR : tcp: fix silent-drop workaround for IPv6 - 2.0, 2.1 - MINOR : logs: Report the true number of retries if there was no connection - 2.0, 2.1 - MINOR : mux-h1: Release idle server H1 connection if data are received - 2.1 - MINOR : http_fetch: make hdr_ip() reject trailing characters - 2.0, 2.1 - MINOR : tools: fix parsing "us" unit for timers - 2.1 - MINOR : http_fetch: make hdr_ip() resistant to empty fields - 2.0, 2.1 - MINOR : server: free srv.lb_nodes in free_server - 2.1 - MINOR : resolvers: Unlink DNS resolution to set RMAINT on SRV resolution - 2.0, 2.1, 2.3 - MINOR : htx: Preserve HTX flags when draining data from an HTX message -- 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: Bugfixes waiting for a release 2.1 (15)
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.1.12 was issued on 2021-03-18. There are currently 15 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2021-04-09 - 8 MEDIUM, first one merged on 2021-03-31 - 5 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.1.13 would be 2021-05-07, which is in two weeks or less. The current list of patches in the queue is: - 2.1 - MAJOR : dns: disabled servers through SRV records never recover - 2.1 - MAJOR : dns: fix null pointer dereference in snr_update_srv_status - 2.1 - MEDIUM : debug/lua: Use internal hlua function to dump the lua traceback - 2.1 - MEDIUM : resolvers: Don't release resolution from a requester callbacks - 2.1 - MEDIUM : freq_ctr/threads: use the global_now_ms variable - 2.1 - MEDIUM : task: close a possible data race condition on a tasklet's list link - 2.1 - MEDIUM : time: make sure to always initialize the global tick - 2.1 - MEDIUM : lua: Always init the lua stack before referencing the context - 2.1 - MEDIUM : mux-h1: make h1_shutw_conn() idempotent - 2.1 - MEDIUM : thread: Fix a deadlock if an isolated thread is marked as harmless - 2.1 - MINOR : resolvers: Unlink DNS resolution to set RMAINT on SRV resolution - 2.1 - MINOR : http_fetch: make hdr_ip() reject trailing characters - 2.1 - MINOR : http_fetch: make hdr_ip() resistant to empty fields - 2.1 - MINOR : tcp: fix silent-drop workaround for IPv6 - 2.1 - MINOR : stats: Apply proper styles in HTML status page. -- 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: Bugfixes waiting for a release 2.3 (5), 2.1 (15)
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.3.9 was issued on 2021-03-30. There are currently 5 patches in the queue cut down this way: - 5 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.3.10 would be 2021-04-28, which is in one week or less. Last release 2.1.12 was issued on 2021-03-18. There are currently 15 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2021-04-09 - 8 MEDIUM, first one merged on 2021-03-31 - 5 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.1.13 would be 2021-05-07, which is in three weeks or less. The current list of patches in the queue is: - 2.1 - MAJOR : dns: disabled servers through SRV records never recover - 2.1 - MAJOR : dns: fix null pointer dereference in snr_update_srv_status - 2.1 - MEDIUM : debug/lua: Use internal hlua function to dump the lua traceback - 2.1 - MEDIUM : task: close a possible data race condition on a tasklet's list link - 2.1 - MEDIUM : resolvers: Don't release resolution from a requester callbacks - 2.1 - MEDIUM : time: make sure to always initialize the global tick - 2.1 - MEDIUM : thread: Fix a deadlock if an isolated thread is marked as harmless - 2.1 - MEDIUM : lua: Always init the lua stack before referencing the context - 2.1 - MEDIUM : freq_ctr/threads: use the global_now_ms variable - 2.1 - MEDIUM : mux-h1: make h1_shutw_conn() idempotent - 2.3 - MINOR : ssl: Prevent removal of crt-list line if the instance is a default one - 2.3 - MINOR : ssl: Fix update of default certificate - 2.1 - MINOR : http_fetch: make hdr_ip() reject trailing characters - 2.1 - MINOR : resolvers: Unlink DNS resolution to set RMAINT on SRV resolution - 2.1, 2.3 - MINOR : http_fetch: make hdr_ip() resistant to empty fields - 2.1 - MINOR : stats: Apply proper styles in HTML status page. - 2.1, 2.3 - MINOR : tcp: fix silent-drop workaround for IPv6 - 2.3 - MINOR : ssl: Add missing free on SSL_CTX in ckch_inst_free -- 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: Bugfixes waiting for a release 2.3 (5), 2.1 (14)
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.3.9 was issued on 2021-03-30. There are currently 5 patches in the queue cut down this way: - 5 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.3.10 would be 2021-04-28, which is in two weeks or less. Last release 2.1.12 was issued on 2021-03-18. There are currently 14 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2021-04-09 - 7 MEDIUM, first one merged on 2021-03-31 - 5 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.1.13 would be 2021-05-07, which is in four weeks or less. The current list of patches in the queue is: - 2.1 - MAJOR : dns: fix null pointer dereference in snr_update_srv_status - 2.1 - MAJOR : dns: disabled servers through SRV records never recover - 2.1 - MEDIUM : thread: Fix a deadlock if an isolated thread is marked as harmless - 2.1 - MEDIUM : freq_ctr/threads: use the global_now_ms variable - 2.1 - MEDIUM : debug/lua: Use internal hlua function to dump the lua traceback - 2.1 - MEDIUM : resolvers: Don't release resolution from a requester callbacks - 2.1 - MEDIUM : time: make sure to always initialize the global tick - 2.1 - MEDIUM : mux-h1: make h1_shutw_conn() idempotent - 2.1 - MEDIUM : lua: Always init the lua stack before referencing the context - 2.1 - MINOR : stats: Apply proper styles in HTML status page. - 2.1, 2.3 - MINOR : tcp: fix silent-drop workaround for IPv6 - 2.1, 2.3 - MINOR : http_fetch: make hdr_ip() resistant to empty fields - 2.3 - MINOR : ssl: Fix update of default certificate - 2.3 - MINOR : ssl: Add missing free on SSL_CTX in ckch_inst_free - 2.1 - MINOR : http_fetch: make hdr_ip() reject trailing characters - 2.1 - MINOR : resolvers: Unlink DNS resolution to set RMAINT on SRV resolution - 2.3 - MINOR : ssl: Prevent removal of crt-list line if the instance is a default one -- 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: Bugfixes waiting for a release 2.3 (5), 2.1 (7), 2.0 (11)
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.3.9 was issued on 2021-03-30. There are currently 5 patches in the queue cut down this way: - 5 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.3.10 would be 2021-04-28, which is in three weeks or less. Last release 2.1.12 was issued on 2021-03-18. There are currently 7 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2021-03-31 - 3 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.1.13 would be 2021-05-26, which is in seven weeks or less. Last release 2.0.21 was issued on 2021-03-18. There are currently 11 patches in the queue cut down this way: - 1 BUG, first one merged on 2021-03-24 - 6 MEDIUM, first one merged on 2021-03-24 - 4 MINOR, first one merged on 2021-03-31 Thus the computed ideal release date for 2.0.22 would be 2021-05-19, which is in six weeks or less. The current list of patches in the queue is: - 2.0 - BUG : mworker/cli: do not use the unix_bind prefix for the master CLI socket - 2.0, 2.1 - MEDIUM : thread: Fix a deadlock if an isolated thread is marked as harmless - 2.0 - MEDIUM : lua: Always init the lua stack before referencing the context - 2.0 - MEDIUM : debug/lua: Use internal hlua function to dump the lua traceback - 2.0, 2.1 - MEDIUM : mux-h1: make h1_shutw_conn() idempotent - 2.0, 2.1 - MEDIUM : freq_ctr/threads: use the global_now_ms variable - 2.0, 2.1 - MEDIUM : time: make sure to always initialize the global tick - 2.0, 2.1 - MINOR : http_fetch: make hdr_ip() reject trailing characters - 2.0, 2.1, 2.3 - MINOR : tcp: fix silent-drop workaround for IPv6 - 2.0 - MINOR : stats: Apply proper styles in HTML status page. - 2.3 - MINOR : ssl: Fix update of default certificate - 2.3 - MINOR : ssl: Add missing free on SSL_CTX in ckch_inst_free - 2.0, 2.1, 2.3 - MINOR : http_fetch: make hdr_ip() resistant to empty fields - 2.3 - MINOR : ssl: Prevent removal of crt-list line if the instance is a default one -- 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: Bugfixes waiting for a release 2.2 (8), 2.0 (4)
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.2.11 was issued on 2021-03-18. There are currently 8 patches in the queue cut down this way: - 1 BUG, first one merged on 2021-03-23 - 6 MEDIUM, first one merged on 2021-03-23 - 1 MINOR, first one merged on 2021-03-24 Thus the computed ideal release date for 2.2.12 would be 2021-04-20, which is in three weeks or less. Last release 2.0.21 was issued on 2021-03-18. There are currently 4 patches in the queue cut down this way: - 1 BUG, first one merged on 2021-03-24 - 3 MEDIUM, first one merged on 2021-03-24 Thus the computed ideal release date for 2.0.22 would be 2021-05-19, which is in seven weeks or less. The current list of patches in the queue is: - 2.0, 2.2 - BUG : mworker/cli: do not use the unix_bind prefix for the master CLI socket - 2.2 - MEDIUM : fd: do not wait on FD removal in fd_delete() - 2.0, 2.2 - MEDIUM : lua: Always init the lua stack before referencing the context - 2.0, 2.2 - MEDIUM : freq_ctr/threads: use the global_now_ms variable - 2.2 - MEDIUM : debug/lua: Don't dump the lua stack if not dumpable - 2.2 - MEDIUM : fd: Take the fd_mig_lock when closing if no DWCAS is available. - 2.0, 2.2 - MEDIUM : debug/lua: Use internal hlua function to dump the lua traceback - 2.2 - MINOR : ssl: Prevent disk access when using "add ssl crt-list" -- 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: Bugfixes waiting for a release 2.3 (6), 2.2 (3)
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.3.7 was issued on 2021-03-16. There are currently 6 patches in the queue cut down this way: - 1 BUG, first one merged on 2021-03-23 - 3 MEDIUM, first one merged on 2021-03-22 - 2 MINOR, first one merged on 2021-03-18 Thus the computed ideal release date for 2.3.8 would be 2021-04-15, which is in three weeks or less. Last release 2.2.11 was issued on 2021-03-18. There are currently 3 patches in the queue cut down this way: - 1 BUG, first one merged on 2021-03-23 - 2 MEDIUM, first one merged on 2021-03-23 Thus the computed ideal release date for 2.2.12 would be 2021-04-20, which is in four weeks or less. The current list of patches in the queue is: - 2.2, 2.3 - BUG : mworker/cli: do not use the unix_bind prefix for the master CLI socket - 2.3 - MEDIUM : mux-fcgi: Fix locking of idle_conns lock in the FCGI I/O callback - 2.2, 2.3 - MEDIUM : debug/lua: Don't dump the lua stack if not dumpable - 2.2, 2.3 - MEDIUM : freq_ctr/threads: use the global_now_ms variable - 2.3 - MINOR : protocol: add missing support of dgram unix socket. - 2.3 - MINOR : freq_ctr/threads: make use of the last updated global time -- 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: Bugfixes waiting for a release 2.2 (10), 2.1 (55), 2.0 (45)
- 2.0, 2.1 - MINOR : sample: check alloc_trash_chunk return value in concat() - 2.2 - MINOR : session: Add some forgotten tests on session's listener - 2.0, 2.1 - MINOR : http-ana: Don't increment HTTP error counter on read error/timeout - 2.0, 2.1 - MINOR : server: Fix server-state-file-name directive - 2.0, 2.1 - MINOR : checks: properly handle wrapping time in __health_adjust() - 2.0, 2.1 - MINOR : mux-h1: Immediately report H1C errors from h1_snd_buf() - 2.0, 2.1 - MINOR : server: re-align state file fields number - 2.0, 2.1 - MINOR : server: Be sure to cut the last parsed field of a server-state line - 2.0, 2.1 - MINOR : tcp-act: Don't forget to set the original port for IPv4 set-dst rule - 2.1 - MINOR : threads: Fixes the number of possible cpus report for Mac. - 2.0, 2.1 - MINOR : tools: Fix a memory leak on error path in parse_dotted_uints() - 2.0, 2.1 - MINOR : config: fix leak on proxy.conn_src.bind_hdr_name - 2.0, 2.1 - MINOR : server: Remove RMAINT from admin state when loading server state - 2.2 - MINOR : tcpcheck: Fix double free on error path when parsing tcp/http-check - 2.2 - MINOR : tcpcheck: Update .health threshold of agent inside an agent-check - 2.0, 2.1 - MINOR : mworker: define _GNU_SOURCE for strsignal() - 2.0, 2.1 - MINOR : sample: secure convs that accept base64 string and var name as args - 2.0, 2.1 - MINOR : resolvers: new callback to properly handle SRV record errors - 2.1 - MINOR : ssl: init tmp chunk correctly in ssl_sock_load_sctl_from_file() - 2.0, 2.1 - MINOR : connection: Use the client's dst family for adressless servers - 2.0, 2.1 - MINOR : session: atomically increment the tracked sessions counter - 2.0, 2.1 - MINOR : xxhash: make sure armv6 uses memcpy() - 2.1 - MINOR : ssl/cli: potential null pointer dereference in "set ssl cert" - 2.0, 2.1 - MINOR : sample: Always consider zero size string samples as unsafe - 2.0, 2.1 - MINOR : proxy: wake up all threads when sending the hard-stop signal - 2.0, 2.1 - MINOR : cfgparse: do not mention "addr:port" as supported on proxy lines - 2.0, 2.1 - MINOR : backend: hold correctly lock when killing idle conn - 2.0, 2.1 - MINOR : init: Use a dynamic buffer to set HAPROXY_CFGFILES env variable - 2.0, 2.1 - MINOR : sample: Memory leak of sample_expr structure in case of error -- 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: Bugfixes waiting for a release 2.3 (4), 2.2 (1), 2.1 (55), 2.0 (45)
- MINOR : server: re-align state file fields number - 2.0, 2.1 - MINOR : checks: properly handle wrapping time in __health_adjust() - 2.0, 2.1 - MINOR : tcp-act: Don't forget to set the original port for IPv4 set-dst rule - 2.1 - MINOR : ssl/cli: potential null pointer dereference in "set ssl cert" - 2.1 - MINOR : threads: Fixes the number of possible cpus report for Mac. - 2.0, 2.1 - MINOR : http-ana: Don't increment HTTP error counter on read error/timeout - 2.0, 2.1 - MINOR : resolvers: new callback to properly handle SRV record errors - 2.0, 2.1 - MINOR : server: Fix server-state-file-name directive - 2.0, 2.1 - MINOR : backend: hold correctly lock when killing idle conn - 2.1 - MINOR : stats: revert the change on ST_CONVDONE - 2.0, 2.1 - MINOR : mworker: define _GNU_SOURCE for strsignal() - 2.0, 2.1 - MINOR : init: Use a dynamic buffer to set HAPROXY_CFGFILES env variable - 2.1 - MINOR : ssl: init tmp chunk correctly in ssl_sock_load_sctl_from_file() - 2.0, 2.1 - MINOR : stick-table: Always call smp_fetch_src() with a valid arg list - 2.3 - MINOR : mt-list: always perform a cpu_relax call on failure - 2.1 - MINOR : mux-h2: Fix typo in scheme adjustment - 2.0, 2.1 - MINOR : sample: Memory leak of sample_expr structure in case of error - 2.0, 2.1 - MINOR : server: Be sure to cut the last parsed field of a server-state line - 2.0, 2.1 - MINOR : server: Init params before parsing a new server-state line - 2.1 - MINOR : mux_h2: missing space between "st" and ".flg" in the "show fd" helper - 2.0, 2.1 - MINOR : session: atomically increment the tracked sessions counter - 2.0, 2.1 - MINOR : config: fix leak on proxy.conn_src.bind_hdr_name - 2.0, 2.1 - MINOR : proxy: wake up all threads when sending the hard-stop signal - 2.0, 2.1 - MINOR : http-ana: Only consider dst address to process originalto option - 2.3 - MINOR : ssl: don't truncate the file descriptor to 16 bits in debug mode - 2.0, 2.1 - MINOR : xxhash: make sure armv6 uses memcpy() -- 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: Bugfixes waiting for a release 2.3 (41), 2.2 (38), 2.1 (50), 2.0 (43)
ort for Mac. - 2.3 - MINOR : stats: fix compare of no-maint url suffix - 2.0, 2.1, 2.2, 2.3- MINOR : server: Remove RMAINT from admin state when loading server state - 2.2, 2.3 - MINOR : resolvers: Fix condition to release received ARs if not assigned - 2.0, 2.1, 2.2, 2.3- MINOR : sample: Always consider zero size string samples as unsafe - 2.0, 2.1, 2.2, 2.3- MINOR : server: Don't call fopen() with server-state filepath set to NULL - 2.0, 2.1 - MINOR : sample: check alloc_trash_chunk return value in concat() - 2.0, 2.1, 2.2, 2.3- MINOR : backend: hold correctly lock when killing idle conn - 2.1 - MINOR : mux_h2: missing space between "st" and ".flg" in the "show fd" helper - 2.0, 2.1, 2.2, 2.3- MINOR : resolvers: new callback to properly handle SRV record errors - 2.2, 2.3 - MINOR : resolvers: Only renew TTL for SRV records with an additional record - 2.0, 2.1, 2.2, 2.3- MINOR : tools: Fix a memory leak on error path in parse_dotted_uints() - 2.0, 2.1, 2.2, 2.3- MINOR : tcp-act: Don't forget to set the original port for IPv4 set-dst rule - 2.0, 2.1 - MINOR : peers: Wrong "new_conn" value for "show peers" CLI command. - 2.0, 2.1, 2.2, 2.3- MINOR : cfgparse: do not mention "addr:port" as supported on proxy lines - 2.0, 2.1 - MINOR : mworker: define _GNU_SOURCE for strsignal() - 2.0, 2.1 - MINOR : config: fix leak on proxy.conn_src.bind_hdr_name - 2.0, 2.1 - MINOR : xxhash: make sure armv6 uses memcpy() - 2.1, 2.2, 2.3 - MINOR : http-ana: Don't increment HTTP error counter on internal errors - 2.1, 2.2, 2.3 - MINOR : ssl/cli: potential null pointer dereference in "set ssl cert" - 2.0, 2.1, 2.2, 2.3- MINOR : sample: secure convs that accept base64 string and var name as args - 2.0, 2.1, 2.2, 2.3- MINOR : http-ana: Only consider dst address to process originalto option - 2.1 - MINOR : ssl: init tmp chunk correctly in ssl_sock_load_sctl_from_file() - 2.2, 2.3 - MINOR : fd: properly wait for !running_mask in fd_set_running_excl() - 2.0, 2.1, 2.2, 2.3- MINOR : server: Be sure to cut the last parsed field of a server-state line - 2.0, 2.1, 2.2, 2.3- MINOR : connection: Use the client's dst family for adressless servers - 2.0, 2.1, 2.2, 2.3- MINOR : proxy: wake up all threads when sending the hard-stop signal - 2.0, 2.1, 2.2, 2.3- MINOR : session: atomically increment the tracked sessions counter -- 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: Bugfixes waiting for a release 2.3 (23), 2.1 (19), 2.0 (15)
t; value for "show peers" CLI command. - 2.3 - MINOR : server: Fix server-state-file-name directive - 2.3 - MINOR : server: re-align state file fields number - 2.1 - MINOR : mux_h2: missing space between "st" and ".flg" in the "show fd" helper - 2.0, 2.1 - MINOR : xxhash: make sure armv6 uses memcpy() - 2.0, 2.1 - MINOR : sample: check alloc_trash_chunk return value in concat() - 2.1 - MINOR : threads: Fixes the number of possible cpus report for Mac. -- 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: Bugfixes waiting for a release 2.1 (19), 2.0 (15)
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.1.11 was issued on 2021-01-08. There are currently 19 patches in the queue cut down this way: - 7 MEDIUM, first one merged on 2021-01-26 - 12 MINOR, first one merged on 2021-01-26 Thus the computed ideal release date for 2.1.12 would be 2021-03-23, which is in five weeks or less. Last release 2.0.20 was issued on 2021-01-08. There are currently 15 patches in the queue cut down this way: - 7 MEDIUM, first one merged on 2021-01-28 - 8 MINOR, first one merged on 2021-01-28 Thus the computed ideal release date for 2.0.21 would be 2021-03-25, which is in five weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MEDIUM : ssl: check a connection's status before computing a handshake - 2.0, 2.1 - MEDIUM : mux-h2: fix read0 handling on partial frames - 2.0 - MEDIUM : mux-h2: Be sure to enter in demux loop even if dbuf is empty - 2.0, 2.1 - MEDIUM : mux-h2: handle remaining read0 cases - 2.1 - MEDIUM : ssl/cli: abort ssl cert is freeing the old store - 2.0, 2.1 - MEDIUM : mux-h2: do not quit the demux loop before setting END_REACHED - 2.0, 2.1 - MEDIUM : filters/htx: Fix data forwarding when payload length is unknown - 2.0, 2.1 - MEDIUM : stats: add missing INF_BUILD_INFO definition - 2.0, 2.1 - MINOR : init: Use a dynamic buffer to set HAPROXY_CFGFILES env variable - 2.0, 2.1 - MINOR : peers: Wrong "new_conn" value for "show peers" CLI command. - 2.0, 2.1 - MINOR : stick-table: Always call smp_fetch_src() with a valid arg list - 2.1 - MINOR : mux_h2: missing space between "st" and ".flg" in the "show fd" helper - 2.0, 2.1 - MINOR : xxhash: make sure armv6 uses memcpy() - 2.0, 2.1 - MINOR : mworker: define _GNU_SOURCE for strsignal() - 2.1 - MINOR : init: enforce strict-limits when using master-worker - 2.1 - MINOR : threads: Fixes the number of possible cpus report for Mac. - 2.0, 2.1 - MINOR : sample: check alloc_trash_chunk return value in concat() - 2.1 - MINOR : ssl: init tmp chunk correctly in ssl_sock_load_sctl_from_file() - 2.0, 2.1 - MINOR : config: fix leak on proxy.conn_src.bind_hdr_name - 2.0, 2.1 - MINOR : sample: Memory leak of sample_expr structure in case of error -- 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: Bugfixes waiting for a release 2.1 (19), 2.0 (14)
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.1.11 was issued on 2021-01-08. There are currently 19 patches in the queue cut down this way: - 7 MEDIUM, first one merged on 2021-01-26 - 12 MINOR, first one merged on 2021-01-26 Thus the computed ideal release date for 2.1.12 would be 2021-03-23, which is in six weeks or less. Last release 2.0.20 was issued on 2021-01-08. There are currently 14 patches in the queue cut down this way: - 6 MEDIUM, first one merged on 2021-01-28 - 8 MINOR, first one merged on 2021-01-28 Thus the computed ideal release date for 2.0.21 would be 2021-03-25, which is in six weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MEDIUM : filters/htx: Fix data forwarding when payload length is unknown - 2.0, 2.1 - MEDIUM : ssl: check a connection's status before computing a handshake - 2.0, 2.1 - MEDIUM : mux-h2: do not quit the demux loop before setting END_REACHED - 2.0, 2.1 - MEDIUM : stats: add missing INF_BUILD_INFO definition - 2.0, 2.1 - MEDIUM : mux-h2: fix read0 handling on partial frames - 2.0, 2.1 - MEDIUM : mux-h2: handle remaining read0 cases - 2.1 - MEDIUM : ssl/cli: abort ssl cert is freeing the old store - 2.0, 2.1 - MINOR : config: fix leak on proxy.conn_src.bind_hdr_name - 2.0, 2.1 - MINOR : peers: Wrong "new_conn" value for "show peers" CLI command. - 2.1 - MINOR : threads: Fixes the number of possible cpus report for Mac. - 2.1 - MINOR : ssl: init tmp chunk correctly in ssl_sock_load_sctl_from_file() - 2.0, 2.1 - MINOR : sample: Memory leak of sample_expr structure in case of error - 2.1 - MINOR : mux_h2: missing space between "st" and ".flg" in the "show fd" helper - 2.0, 2.1 - MINOR : stick-table: Always call smp_fetch_src() with a valid arg list - 2.0, 2.1 - MINOR : init: Use a dynamic buffer to set HAPROXY_CFGFILES env variable - 2.0, 2.1 - MINOR : xxhash: make sure armv6 uses memcpy() - 2.0, 2.1 - MINOR : sample: check alloc_trash_chunk return value in concat() - 2.0, 2.1 - MINOR : mworker: define _GNU_SOURCE for strsignal() - 2.1 - MINOR : init: enforce strict-limits when using master-worker -- 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: Bugfixes waiting for a release 2.3 (16), 2.2 (10), 2.1 (11), 2.0 (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 2.3.4 was issued on 2021-01-13. There are currently 16 patches in the queue cut down this way: - 6 MEDIUM, first one merged on 2021-01-26 - 10 MINOR, first one merged on 2021-01-26 Thus the computed ideal release date for 2.3.5 would be 2021-02-23, which is in three weeks or less. Last release 2.2.8 was issued on 2021-01-13. There are currently 10 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2021-01-26 - 7 MINOR, first one merged on 2021-01-26 Thus the computed ideal release date for 2.2.9 would be 2021-02-23, which is in three weeks or less. Last release 2.1.11 was issued on 2021-01-08. There are currently 11 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2021-01-26 - 8 MINOR, first one merged on 2021-01-26 Thus the computed ideal release date for 2.1.12 would be 2021-03-23, which is in seven weeks or less. Last release 2.0.20 was issued on 2021-01-08. There are currently 8 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2021-01-28 - 5 MINOR, first one merged on 2021-01-28 Thus the computed ideal release date for 2.0.21 would be 2021-03-25, which is in seven weeks or less. The current list of patches in the queue is: - 2.3 - MEDIUM : tcpcheck: Don't destroy connection in the wake callback context - 2.3 - MEDIUM : session: only retrieve ready idle conn from session - 2.0, 2.1, 2.2, 2.3- MEDIUM : mux-h2: fix read0 handling on partial frames - 2.0, 2.1, 2.2, 2.3- MEDIUM : stats: add missing INF_BUILD_INFO definition - 2.0, 2.1, 2.2, 2.3- MEDIUM : filters/htx: Fix data forwarding when payload length is unknown - 2.3 - MEDIUM : backend: never reuse a connection for tcp mode - 2.2, 2.3 - MINOR : peers: Possible appctx pointer dereference. - 2.0, 2.1, 2.2, 2.3- MINOR : peers: Wrong "new_conn" value for "show peers" CLI command. - 2.1, 2.2, 2.3 - MINOR : threads: Fixes the number of possible cpus report for Mac. - 2.1, 2.2, 2.3 - MINOR : mux_h2: missing space between "st" and ".flg" in the "show fd" helper - 2.0, 2.1 - MINOR : sample: Memory leak of sample_expr structure in case of error - 2.0, 2.1, 2.2, 2.3- MINOR : init: Use a dynamic buffer to set HAPROXY_CFGFILES env variable - 2.0, 2.1 - MINOR : sample: check alloc_trash_chunk return value in concat() - 2.1 - MINOR : init: enforce strict-limits when using master-worker - 2.3 - MINOR : config: fix leak on proxy.conn_src.bind_hdr_name - 2.3 - MINOR : backend: check available list allocation for reuse - 2.2, 2.3 - MINOR : dns: SRV records ignores duplicated AR records (v2) - 2.0, 2.1, 2.2, 2.3- MINOR : mworker: define _GNU_SOURCE for strsignal() - 2.3 - MINOR : ssl: init tmp chunk correctly in ssl_sock_load_sctl_from_file() -- 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: Bugfixes waiting for a release 2.3 (11), 2.2 (10)
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.3.4 was issued on 2021-01-13. There are currently 11 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2021-01-26 - 7 MINOR, first one merged on 2021-01-26 Thus the computed ideal release date for 2.3.5 would be 2021-02-23, which is in four weeks or less. Last release 2.2.8 was issued on 2021-01-13. There are currently 10 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2021-01-26 - 7 MINOR, first one merged on 2021-01-26 Thus the computed ideal release date for 2.2.9 would be 2021-02-23, which is in four weeks or less. The current list of patches in the queue is: - 2.3 - MEDIUM : tcpcheck: Don't destroy connection in the wake callback context - 2.2, 2.3 - MEDIUM : stats: add missing INF_BUILD_INFO definition - 2.2, 2.3 - MEDIUM : mux-h2: fix read0 handling on partial frames - 2.2, 2.3 - MEDIUM : filters/htx: Fix data forwarding when payload length is unknown - 2.2, 2.3 - MINOR : peers: Wrong "new_conn" value for "show peers" CLI command. - 2.2, 2.3 - MINOR : init: Use a dynamic buffer to set HAPROXY_CFGFILES env variable - 2.2, 2.3 - MINOR : mworker: define _GNU_SOURCE for strsignal() - 2.2, 2.3 - MINOR : peers: Possible appctx pointer dereference. - 2.2, 2.3 - MINOR : threads: Fixes the number of possible cpus report for Mac. - 2.2, 2.3 - MINOR : dns: SRV records ignores duplicated AR records (v2) - 2.2, 2.3 - MINOR : mux_h2: missing space between "st" and ".flg" in the "show fd" helper -- 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: Bugfixes waiting for a release 2.3 (23), 2.2 (17), 2.1 (26), 2.0 (24)
check its parameters - 2.2, 2.3 - MINOR : mux-h1: Handle keep-alive timeout for idle frontend connections - 2.0, 2.1 - MINOR : peers: Do not ignore a protocol error for dictionary entries. - 2.1 - MINOR : http-htx: Just warn if payload of an errorfile doesn't match the C-L -- 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: Bugfixes waiting for a release 2.3 (23), 2.2 (17), 2.1 (26), 2.0 (24)
: tools: make parse_time_err() more strict on the timer validity - 2.3 - MINOR : mux-h2/stats: not all GOAWAY frames are errors - 2.3 - MINOR : mux-h2/stats: make stream/connection proto errors more accurate - 2.0, 2.1, 2.2, 2.3- MINOR : tools: Reject size format not starting by a digit -- 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: Bugfixes waiting for a release 2.3 (23), 2.2 (17), 2.1 (26), 2.0 (24)
- 2.0, 2.1 - MINOR : lua: set buffer size during map lookups - 2.0, 2.1 - MINOR : http-fetch: Extract cookie value even when no cookie name - 2.0, 2.1, 2.2, 2.3- MINOR : lua: Some lua init operation are processed unsafe - 2.0, 2.1 - MINOR : pattern: a sample marked as const could be written -- 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: Bugfixes waiting for a release 2.3 (23), 2.2 (17), 2.1 (26), 2.0 (24)
- MINOR : http-htx: Just warn if payload of an errorfile doesn't match the C-L - 2.2, 2.3 - MINOR : tcpcheck: Don't rearm the check timeout on each read - 2.0, 2.1, 2.2, 2.3- MINOR : lua: lua-load doesn't check its parameters - 2.1, 2.2, 2.3 - MINOR : lua: missing "\n" in error message -- 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: Bugfixes waiting for a release 2.1 (12), 2.0 (11)
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.1.10 was issued on 2020-11-05. There are currently 12 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-11-13 - 2 MEDIUM, first one merged on 2020-11-13 - 8 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.1.11 would be 2020-12-11, which is in one week or less. Last release 2.0.19 was issued on 2020-11-06. There are currently 11 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-11-13 - 2 MEDIUM, first one merged on 2020-11-13 - 7 MINOR, first one merged on 2020-11-13 Thus the computed ideal release date for 2.0.20 would be 2020-12-11, which is in one week or less. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : spoe: Be sure to remove all references on a released spoe applet - 2.0, 2.1 - MAJOR : filters: Always keep all offsets up to date during data filtering - 2.0, 2.1 - MEDIUM : peers: fix decoding of multi-byte length in stick-table messages - 2.0, 2.1 - MEDIUM : filters: Forward all filtered data at the end of http filtering - 2.0, 2.1 - MINOR : http-ana: Don't wait for the body of CONNECT requests - 2.1 - MINOR : http-htx: Just warn if payload of an errorfile doesn't match the C-L - 2.0, 2.1 - MINOR : lua: set buffer size during map lookups - 2.0, 2.1 - MINOR : pattern: a sample marked as const could be written - 2.0, 2.1 - MINOR : peers: Do not ignore a protocol error for dictionary entries. - 2.0, 2.1 - MINOR : http-fetch: Extract cookie value even when no cookie name - 2.0, 2.1 - MINOR : http-fetch: Fix calls w/o parentheses of the cookie sample fetches - 2.0, 2.1 - MINOR : peers: Missing TX cache entries reset. -- 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: Bugfixes waiting for a release 2.1 (12), 2.0 (11)
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.1.10 was issued on 2020-11-05. There are currently 12 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-11-13 - 2 MEDIUM, first one merged on 2020-11-13 - 8 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.1.11 would be 2020-12-11, which is in two weeks or less. Last release 2.0.19 was issued on 2020-11-06. There are currently 11 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-11-13 - 2 MEDIUM, first one merged on 2020-11-13 - 7 MINOR, first one merged on 2020-11-13 Thus the computed ideal release date for 2.0.20 would be 2020-12-11, which is in two weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : spoe: Be sure to remove all references on a released spoe applet - 2.0, 2.1 - MAJOR : filters: Always keep all offsets up to date during data filtering - 2.0, 2.1 - MEDIUM : peers: fix decoding of multi-byte length in stick-table messages - 2.0, 2.1 - MEDIUM : filters: Forward all filtered data at the end of http filtering - 2.0, 2.1 - MINOR : http-fetch: Extract cookie value even when no cookie name - 2.0, 2.1 - MINOR : lua: set buffer size during map lookups - 2.1 - MINOR : http-htx: Just warn if payload of an errorfile doesn't match the C-L - 2.0, 2.1 - MINOR : http-fetch: Fix calls w/o parentheses of the cookie sample fetches - 2.0, 2.1 - MINOR : peers: Do not ignore a protocol error for dictionary entries. - 2.0, 2.1 - MINOR : pattern: a sample marked as const could be written - 2.0, 2.1 - MINOR : peers: Missing TX cache entries reset. - 2.0, 2.1 - MINOR : http-ana: Don't wait for the body of CONNECT requests -- 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: Bugfixes waiting for a release 2.2 (14), 2.1 (9), 2.0 (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 2.2.5 was issued on 2020-11-05. There are currently 14 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-11-13 - 2 MEDIUM, first one merged on 2020-11-13 - 11 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.2.6 would be 2020-11-27, which is in two weeks or less. Last release 2.1.10 was issued on 2020-11-05. There are currently 9 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-11-13 - 1 MEDIUM, first one merged on 2020-11-13 - 7 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.1.11 would be 2020-11-27, which is in two weeks or less. Last release 2.0.19 was issued on 2020-11-06. There are currently 8 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-11-13 - 1 MEDIUM, first one merged on 2020-11-13 - 6 MINOR, first one merged on 2020-11-13 Thus the computed ideal release date for 2.0.20 would be 2020-12-11, which is in four weeks or less. The current list of patches in the queue is: - 2.0, 2.1, 2.2 - MAJOR : spoe: Be sure to remove all references on a released spoe applet - 2.2 - MEDIUM : check: reuse srv proto only if using same mode - 2.0, 2.1, 2.2 - MEDIUM : peers: fix decoding of multi-byte length in stick-table messages - 2.2 - MINOR : ssl: don't report 1024 bits DH param load error when it's higher - 2.2 - MINOR : tcpcheck: Don't warn on unused rules if check option is after - 2.2 - MINOR : http-htx: Handle warnings when parsing http-error and http-errors - 2.0, 2.1, 2.2 - MINOR : peers: Missing TX cache entries reset. - 2.1, 2.2 - MINOR : http-htx: Just warn if payload of an errorfile doesn't match the C-L - 2.0, 2.1, 2.2 - MINOR : lua: set buffer size during map lookups - 2.0, 2.1, 2.2 - MINOR : peers: Do not ignore a protocol error for dictionary entries. - 2.0, 2.1, 2.2 - MINOR : pattern: a sample marked as const could be written - 2.2 - MINOR : ssl: double free w/ smp_fetch_ssl_x_chain_der() - 2.0, 2.1, 2.2 - MINOR : http-fetch: Fix calls w/o parentheses of the cookie sample fetches - 2.0, 2.1, 2.2 - MINOR : http-fetch: Extract cookie value even when no cookie name -- 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: Bugfixes waiting for a release 2.3 (2), 2.2 (3), 2.1 (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 to this mail must be sent to the mailing list. Last release 2.3.0 was issued on 2020-11-05. There are currently 2 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2020-11-06 - 1 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.3.1 would be 2020-12-04, which is in four weeks or less. Last release 2.2.5 was issued on 2020-11-05. There are currently 3 patches in the queue cut down this way: - 3 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.2.6 would be 2020-12-04, which is in four weeks or less. Last release 2.1.10 was issued on 2020-11-05. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.1.11 would be 2020-12-04, which is in four weeks or less. The current list of patches in the queue is: - 2.3 - MEDIUM : ssl/crt-list: correctly insert crt-list line if crt already loaded - 2.1, 2.2 - MINOR : http-htx: Just warn if payload of an errorfile doesn't match the C-L - 2.2 - MINOR : ssl: double free w/ smp_fetch_ssl_x_chain_der() - 2.2, 2.3 - MINOR : ssl: don't report 1024 bits DH param load error when it's higher -- 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: Bugfixes waiting for a release 2.2 (40), 2.1 (35), 2.0 (30), 1.8 (20)
- MINOR : tcpcheck: Set socks4 and send-proxy flags before the connect call - 1.8 - MINOR : threads: work around a libgcc_s issue with chrooting - 2.0, 2.1, 2.2 - MINOR : http-htx: Expect no body for 204/304 internal HTTP responses - 1.8 - MINOR : startup: haproxy -s cause 100% cpu - 2.2 - MINOR : log: fix risk of null deref on error path - 2.0, 2.1, 2.2 - MINOR : peers: Inconsistency when dumping peer status codes. - 1.8 - MINOR : config: Fix memory leak on config parse listen - 2.0, 2.1, 2.2 - MINOR : cache: Inverted variables in http_calc_maxage function - 2.0, 2.1, 2.2 - MINOR : queue: properly report redistributed connections - 2.1, 2.2 - MINOR : cache: Manage multiple values in cache-control header value - 2.0, 2.1, 2.2 - MINOR : http-ana: Don't send payload for internal responses to HEAD requests - 2.2 - MINOR : checks: Report a socket error before any connection attempt - 1.8, 2.0, 2.1, 2.2- MINOR : stats: fix validity of the json schema - 1.8 - MINOR : dns: ignore trailing dot - 2.1, 2.2 - MINOR : disable dynamic OCSP load with BoringSSL - 1.8 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 2.2 - MINOR : http: Fix content-length of the default 500 error - 2.0, 2.1, 2.2 - MINOR : log: fix memory leak on logsrv parse error - 2.0, 2.1, 2.2 - MINOR : lua: initialize sample before using it - 2.0, 2.1, 2.2 - MINOR : mux-h2: do not stop outgoing connections on stopping - 1.8 - MINOR : ssl: verifyhost is case sensitive - 1.8 - MINOR : stats: use strncmp() instead of memcmp() on health states - 1.8 - MINOR : reload: do not fail when no socket is sent - 2.0, 2.1, 2.2 - MINOR : server: fix srv downtime calcul on starting - 2.1, 2.2 - MINOR : proxy/server: Skip per-proxy/server post-check for disabled proxies - 2.0, 2.1, 2.2 - MINOR : filters: Skip disabled proxies during startup only -- 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: Bugfixes waiting for a release 2.2 (25), 2.1 (18), 2.0 (15), 1.8 (20)
- MINOR : connection: fix loop iter on connection takeover - 2.2 - MINOR : queue: properly report redistributed connections - 2.0, 2.1, 2.2 - MINOR : init: only keep rlim_fd_cur if max is unlimited - 2.0, 2.1, 2.2 - MINOR : peers: Inconsistency when dumping peer status codes. - 1.8 - MINOR : startup: haproxy -s cause 100% cpu - 1.8 - MINOR : ssl: verifyhost is case sensitive - 1.8 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 1.8 - MINOR : config: Fix memory leak on config parse listen - 1.8 - MINOR : stats: use strncmp() instead of memcmp() on health states - 2.0, 2.1, 2.2 - MINOR : Fix several leaks of 'log_tag' in init(). -- 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: Bugfixes waiting for a release 2.2 (20), 2.1 (16), 2.0 (15), 1.8 (20)
- MINOR : peers: Possible unexpected peer seesion reset after collisions. - 1.8 - MINOR : reload: do not fail when no socket is sent - 2.0, 2.1, 2.2 - MINOR : Fix several leaks of 'log_tag' in init(). - 1.8 - MINOR : config: Fix memory leak on config parse listen -- 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: Bugfixes waiting for a release 2.2 (11), 2.1 (9), 2.0 (7), 1.8 (18)
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.2.4 was issued on 2020-09-30. There are currently 11 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2020-10-02 - 8 MINOR, first one merged on 2020-10-02 Thus the computed ideal release date for 2.2.5 would be 2020-10-30, which is in three weeks or less. Last release 2.1.9 was issued on 2020-09-30. There are currently 9 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-09-30 - 5 MINOR, first one merged on 2020-10-08 Thus the computed ideal release date for 2.1.10 would be 2020-10-30, which is in three weeks or less. Last release 2.0.18 was issued on 2020-09-30. There are currently 7 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2020-10-08 - 5 MINOR, first one merged on 2020-10-08 Thus the computed ideal release date for 2.0.19 would be 2020-12-03, which is in seven weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 18 patches in the queue cut down this way: - 8 MEDIUM, first one merged on 2020-08-05 - 10 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in two weeks or less. The current list of patches in the queue is: - 2.0, 2.1, 2.2 - MEDIUM : mux-h2: Don't handle pending read0 too early on streams - 1.8 - MEDIUM : h2: report frame bits only for handled types - 2.1, 2.2 - MEDIUM : mux-fcgi: Don't handle pending read0 too early on streams - 2.1 - MEDIUM : ssl: crt-list negative filters don't work - 1.8 - MEDIUM : ssl: check OCSP calloc in ssl_sock_load_ocsp() - 1.8 - MEDIUM : pattern: fix memory leak in regex pattern functions - 1.8 - MEDIUM : map/lua: Return an error if a map is loaded during runtime - 1.8 - MEDIUM : pattern: Renew the pattern expression revision when it is pruned - 1.8 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 1.8 - MEDIUM : ssl: does not look for all SNIs before chosing a certificate - 1.8 - MEDIUM : listeners: do not pause foreign listeners - 2.0, 2.1, 2.2 - MEDIUM : queue: make pendconn_cond_unlink() really thread-safe - 1.8 - MINOR : stats: use strncmp() instead of memcmp() on health states - 2.2 - MINOR : http: Fix content-length of the default 500 error - 1.8 - MINOR : startup: haproxy -s cause 100% cpu - 1.8 - MINOR : config: Fix memory leak on config parse listen - 1.8, 2.0, 2.1, 2.2- MINOR : stats: fix validity of the json schema - 2.0, 2.1, 2.2 - MINOR : http-htx: Expect no body for 204/304 internal HTTP responses - 1.8 - MINOR : ssl: verifyhost is case sensitive - 2.0, 2.1, 2.2 - MINOR : peers: Inconsistency when dumping peer status codes. - 1.8 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 1.8 - MINOR : dns: ignore trailing dot - 1.8 - MINOR : threads: work around a libgcc_s issue with chrooting - 1.8 - MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 2.0, 2.1, 2.2 - MINOR : mux-h1: Always set the session on frontend h1 stream - 2.2 - MINOR : mux-h1: Be sure to only set CO_RFL_READ_ONCE for the first read - 1.8 - MINOR : reload: do not fail when no socket is sent - 2.2 - MINOR : tcpcheck: Set socks4 and send-proxy flags before the connect call - 2.0, 2.1, 2.2 - MINOR : Fix several leaks of 'log_tag' in init(). -- 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: Bugfixes waiting for a release 2.2 (3), 2.1 (1), 1.8 (17)
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.2.4 was issued on 2020-09-30. There are currently 3 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2020-10-02 - 2 MINOR, first one merged on 2020-10-02 Thus the computed ideal release date for 2.2.5 would be 2020-10-30, which is in four weeks or less. Last release 2.1.9 was issued on 2020-09-30. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2020-09-30 Thus the computed ideal release date for 2.1.10 would be 2020-10-30, which is in four weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 17 patches in the queue cut down this way: - 8 MEDIUM, first one merged on 2020-08-05 - 9 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in three weeks or less. The current list of patches in the queue is: - 1.8 - MEDIUM : h2: report frame bits only for handled types - 1.8 - MEDIUM : ssl: does not look for all SNIs before chosing a certificate - 1.8 - MEDIUM : pattern: Renew the pattern expression revision when it is pruned - 1.8 - MEDIUM : listeners: do not pause foreign listeners - 1.8 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 2.1 - MEDIUM : ssl: crt-list negative filters don't work - 2.2 - MEDIUM : queue: make pendconn_cond_unlink() really thread-safe - 1.8 - MEDIUM : map/lua: Return an error if a map is loaded during runtime - 1.8 - MEDIUM : pattern: fix memory leak in regex pattern functions - 1.8 - MEDIUM : ssl: check OCSP calloc in ssl_sock_load_ocsp() - 1.8 - MINOR : config: Fix memory leak on config parse listen - 1.8 - MINOR : reload: do not fail when no socket is sent - 1.8 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 2.2 - MINOR : Fix several leaks of 'log_tag' in init(). - 1.8 - MINOR : startup: haproxy -s cause 100% cpu - 1.8 - MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 1.8 - MINOR : threads: work around a libgcc_s issue with chrooting - 1.8 - MINOR : ssl: verifyhost is case sensitive - 1.8 - MINOR : dns: ignore trailing dot - 2.2 - MINOR : tcpcheck: Set socks4 and send-proxy flags before the connect call - 1.8 - MINOR : stats: use strncmp() instead of memcmp() on health states -- 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: Bugfixes waiting for a release 2.2 (11), 2.1 (36), 2.0 (26), 1.8 (12)
: threads: work around a libgcc_s issue with chrooting - 2.1, 2.2 - MINOR : Fix memory leaks cfg_parse_peers - 2.2 - MINOR : ssl/crt-list: crt-list could end without a \n - 1.8, 2.0, 2.1 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 2.0, 2.1 - MINOR : auth: report valid crypto(3) support depending on build options - 2.1 - MINOR : converters: Store the sink in an arg pointer for debug() converter - 2.1 - MINOR : lua: Duplicate map name to load it when a new Map object is created - 2.1 - MINOR : http-rules: Replace path and query-string in "replace-path" action - 2.0, 2.1 - MINOR : contrib/spoa-server: Do not free reference to NULL - 1.8 - MINOR : dns: ignore trailing dot -- 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: Bugfixes waiting for a release 2.2 (11), 2.1 (34), 2.0 (26), 1.8 (11)
query-string in "replace-path" action - 2.0, 2.1, 2.2 - MINOR : server: report correct error message for invalid port on "socks4" - 1.8, 2.0, 2.1 - MINOR : threads: work around a libgcc_s issue with chrooting - 2.0, 2.1, 2.2 - MINOR : ssl: verifyhost is case sensitive - 2.0, 2.1 - MINOR : contrib/spoa-server: Do not free reference to NULL - 1.8, 2.0, 2.1 - MINOR : stats: use strncmp() instead of memcmp() on health states - 2.1 - MINOR : ssl: fix memory leak at OCSP loading - 2.2 - MINOR : Fix type passed of sizeof() for calloc() - 1.8 - MINOR : dns: ignore trailing dot - 2.0, 2.1 - MINOR : snapshots: leak of snapshots on deinit() -- 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: Bugfixes waiting for a release 2.2 (1), 2.1 (28), 2.0 (21), 1.8 (11)
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.2.3 was issued on 2020-09-08. There are currently 1 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2020-09-11 Thus the computed ideal release date for 2.2.4 would be 2020-10-11, which is in four weeks or less. Last release 2.1.8 was issued on 2020-07-31. There are currently 28 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-09-07 - 9 MEDIUM, first one merged on 2020-08-05 - 18 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which was one week ago. Last release 2.0.17 was issued on 2020-07-31. There are currently 21 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-09-07 - 9 MEDIUM, first one merged on 2020-08-05 - 11 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is in three weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 11 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-08-05 - 7 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in six weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : contrib/spoa-server: Fix unhandled python call leading to memory leak - 2.0, 2.1 - MEDIUM : contrib/spoa-server: Fix ipv4_address used instead of ipv6_address - 2.0, 2.1 - MEDIUM : doc: Fix replace-path action description - 2.1 - MEDIUM : ssl: memory leak of ocsp data at SSL_CTX_free() - 2.0, 2.1 - MEDIUM : mux-h1: Refresh H1 connection timeout after a synchronous send - 1.8, 2.0, 2.1 - MEDIUM : map/lua: Return an error if a map is loaded during runtime - 2.0, 2.1 - MEDIUM : htx: smp_prefetch_htx() must always validate the direction - 2.0, 2.1 - MEDIUM : mux-h1: always apply the timeout on half-closed connections - 1.8, 2.0, 2.1, 2.2- MEDIUM : pattern: Renew the pattern expression revision when it is pruned - 1.8, 2.0 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 1.8, 2.0, 2.1 - MEDIUM : ssl: check OCSP calloc in ssl_sock_load_ocsp() - 1.8, 2.0, 2.1 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 2.0, 2.1 - MINOR : contrib/spoa-server: Updating references to free in case of failure - 2.1 - MINOR : ssl: fix memory leak at OCSP loading - 1.8, 2.0, 2.1 - MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 2.1 - MINOR : http-rules: Replace path and query-string in "replace-path" action - 1.8, 2.0, 2.1 - MINOR : reload: do not fail when no socket is sent - 1.8, 2.0, 2.1 - MINOR : threads: work around a libgcc_s issue with chrooting - 2.0, 2.1 - MINOR : snapshots: leak of snapshots on deinit() - 2.1 - MINOR : converters: Store the sink in an arg pointer for debug() converter - 1.8 - MINOR : dns: ignore trailing dot - 2.1 - MINOR : lua: Duplicate lua strings in sample fetches/converters arg array - 1.8, 2.0, 2.1 - MINOR : stats: use strncmp() instead of memcmp() on health states - 1.8, 2.0, 2.1 - MINOR : startup: haproxy -s cause 100% cpu - 2.0, 2.1 - MINOR : contrib/spoa-server: Ensure ip address references are freed - 2.0, 2.1 - MINOR : auth: report valid crypto(3) support depending on build options - 2.1 - MINOR : arg: Fix leaks during arguments validation for fetches/converters - 2.1 - MINOR : lua: Duplicate map name to load it when a new Map object is created - 2.0, 2.1 - MINOR : contrib/spoa-server: Do not free reference to NULL - 2.1 - MINOR : http-rules: Replace path and query-string in "replace-path" action" -- 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: Bugfixes waiting for a release 2.1 (23), 2.0 (16), 1.8 (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 2.1.8 was issued on 2020-07-31. There are currently 23 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-09-07 - 6 MEDIUM, first one merged on 2020-08-05 - 16 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which was within the last week. Last release 2.0.17 was issued on 2020-07-31. There are currently 16 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-09-07 - 6 MEDIUM, first one merged on 2020-08-05 - 9 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is in four weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 8 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2020-08-05 - 6 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in seven weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : contrib/spoa-server: Fix unhandled python call leading to memory leak - 2.0, 2.1 - MEDIUM : mux-h1: Refresh H1 connection timeout after a synchronous send - 1.8, 2.0 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 2.0, 2.1 - MEDIUM : doc: Fix replace-path action description - 2.0, 2.1 - MEDIUM : htx: smp_prefetch_htx() must always validate the direction - 2.0, 2.1 - MEDIUM : contrib/spoa-server: Fix ipv4_address used instead of ipv6_address - 2.1 - MEDIUM : ssl: memory leak of ocsp data at SSL_CTX_free() - 1.8, 2.0, 2.1 - MEDIUM : map/lua: Return an error if a map is loaded during runtime - 2.1 - MINOR : http-rules: Replace path and query-string in "replace-path" action - 1.8, 2.0, 2.1 - MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 2.0, 2.1 - MINOR : snapshots: leak of snapshots on deinit() - 1.8 - MINOR : dns: ignore trailing dot - 2.1 - MINOR : ssl: fix memory leak at OCSP loading - 1.8, 2.0, 2.1 - MINOR : startup: haproxy -s cause 100% cpu - 1.8, 2.0, 2.1 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 1.8, 2.0, 2.1 - MINOR : stats: use strncmp() instead of memcmp() on health states - 2.0, 2.1 - MINOR : contrib/spoa-server: Ensure ip address references are freed - 2.1 - MINOR : lua: Duplicate lua strings in sample fetches/converters arg array - 2.0, 2.1 - MINOR : contrib/spoa-server: Do not free reference to NULL - 1.8, 2.0, 2.1 - MINOR : reload: do not fail when no socket is sent - 2.1 - MINOR : http-rules: Replace path and query-string in "replace-path" action" - 2.1 - MINOR : arg: Fix leaks during arguments validation for fetches/converters - 2.0, 2.1 - MINOR : contrib/spoa-server: Updating references to free in case of failure - 2.1 - MINOR : converters: Store the sink in an arg pointer for debug() converter - 2.1 - MINOR : lua: Duplicate map name to load it when a new Map object is created -- 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: Bugfixes waiting for a release 2.2 (23), 2.1 (15), 2.0 (8), 1.8 (6)
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.2.2 was issued on 2020-07-31. There are currently 23 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-08-05 - 9 MEDIUM, first one merged on 2020-08-05 - 13 MINOR, first one merged on 2020-08-05 Thus the computed ideal release date for 2.2.3 would be 2020-08-19, which was two weeks ago. Last release 2.1.8 was issued on 2020-07-31. There are currently 15 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-08-05 - 11 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which is in one week or less. Last release 2.0.17 was issued on 2020-07-31. There are currently 8 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is in five weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 6 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in eight weeks or less. The current list of patches in the queue is: - 2.2 - MAJOR : dns: disabled servers through SRV records never recover - 2.2 - MEDIUM : ssl: never generates the chain from the verify store - 2.0, 2.1, 2.2 - MEDIUM : mux-h1: Refresh H1 connection timeout after a synchronous send - 2.2 - MEDIUM : ssl: fix ssl_bind_conf double free w/ wildcards - 2.1, 2.2 - MEDIUM : ssl: memory leak of ocsp data at SSL_CTX_free() - 1.8, 2.0 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 2.0, 2.1, 2.2 - MEDIUM : htx: smp_prefetch_htx() must always validate the direction - 1.8, 2.0, 2.1, 2.2- MEDIUM : map/lua: Return an error if a map is loaded during runtime - 2.2 - MEDIUM : ssl: crt-list negative filters don't work - 2.2 - MEDIUM : http-ana: Don't wait to send 1xx responses received from servers - 2.2 - MEDIUM : ssl: fix the ssl-skip-self-issued-ca option - 2.1, 2.2 - MINOR : reload: do not fail when no socket is sent - 2.0, 2.1, 2.2 - MINOR : snapshots: leak of snapshots on deinit() - 2.1, 2.2 - MINOR : converters: Store the sink in an arg pointer for debug() converter - 1.8 - MINOR : dns: ignore trailing dot - 2.1, 2.2 - MINOR : arg: Fix leaks during arguments validation for fetches/converters - 2.1, 2.2 - MINOR : lua: Duplicate map name to load it when a new Map object is created - 2.2 - MINOR : ssl: ssl-skip-self-issued-ca requires >= 1.0.2 - 2.1, 2.2 - MINOR : ssl: fix memory leak at OCSP loading - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IP mask in arg validation - 2.1, 2.2 - MINOR : lua: Duplicate lua strings in sample fetches/converters arg array - 2.2 - MINOR : spoa-server: fix size_t format printing - 1.8, 2.0, 2.1, 2.2- MINOR : stats: use strncmp() instead of memcmp() on health states - 2.1, 2.2 - MINOR : http-rules: Replace path and query-string in "replace-path" action - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation -- 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: Bugfixes waiting for a release 2.2 (18), 2.1 (13), 2.0 (8), 1.8 (6)
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.2.2 was issued on 2020-07-31. There are currently 18 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-08-05 - 6 MEDIUM, first one merged on 2020-08-05 - 11 MINOR, first one merged on 2020-08-05 Thus the computed ideal release date for 2.2.3 would be 2020-08-19, which was one week ago. Last release 2.1.8 was issued on 2020-07-31. There are currently 13 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-08-05 - 9 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which is in two weeks or less. Last release 2.0.17 was issued on 2020-07-31. There are currently 8 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is in six weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 6 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in nine weeks or less. The current list of patches in the queue is: - 2.2 - MAJOR : dns: disabled servers through SRV records never recover - 2.2 - MEDIUM : ssl: never generates the chain from the verify store - 2.1, 2.2 - MEDIUM : ssl: memory leak of ocsp data at SSL_CTX_free() - 1.8, 2.0 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 2.0, 2.1, 2.2 - MEDIUM : mux-h1: Refresh H1 connection timeout after a synchronous send - 2.2 - MEDIUM : ssl: fix the ssl-skip-self-issued-ca option - 1.8, 2.0, 2.1, 2.2- MEDIUM : map/lua: Return an error if a map is loaded during runtime - 2.0, 2.1, 2.2 - MEDIUM : htx: smp_prefetch_htx() must always validate the direction - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 2.1, 2.2 - MINOR : ssl: fix memory leak at OCSP loading - 2.1, 2.2 - MINOR : lua: Duplicate map name to load it when a new Map object is created - 2.1, 2.2 - MINOR : arg: Fix leaks during arguments validation for fetches/converters - 1.8 - MINOR : dns: ignore trailing dot - 2.0, 2.1, 2.2 - MINOR : snapshots: leak of snapshots on deinit() - 2.1, 2.2 - MINOR : converters: Store the sink in an arg pointer for debug() converter - 2.2 - MINOR : ssl: ssl-skip-self-issued-ca requires >= 1.0.2 - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IP mask in arg validation - 2.1, 2.2 - MINOR : lua: Duplicate lua strings in sample fetches/converters arg array - 1.8, 2.0, 2.1, 2.2- MINOR : stats: use strncmp() instead of memcmp() on health states - 2.2 - MINOR : spoa-server: fix size_t format printing -- 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: Bugfixes waiting for a release 2.2 (18), 2.1 (13), 2.0 (8), 1.8 (6)
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.2.2 was issued on 2020-07-31. There are currently 18 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-08-05 - 6 MEDIUM, first one merged on 2020-08-05 - 11 MINOR, first one merged on 2020-08-05 Thus the computed ideal release date for 2.2.3 would be 2020-08-19, which was within the last week. Last release 2.1.8 was issued on 2020-07-31. There are currently 13 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-08-05 - 9 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which is in three weeks or less. Last release 2.0.17 was issued on 2020-07-31. There are currently 8 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is in seven weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 6 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in ten weeks or less. The current list of patches in the queue is: - 2.2 - MAJOR : dns: disabled servers through SRV records never recover - 2.2 - MEDIUM : ssl: fix the ssl-skip-self-issued-ca option - 1.8, 2.0 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 2.2 - MEDIUM : ssl: never generates the chain from the verify store - 2.0, 2.1, 2.2 - MEDIUM : mux-h1: Refresh H1 connection timeout after a synchronous send - 2.0, 2.1, 2.2 - MEDIUM : htx: smp_prefetch_htx() must always validate the direction - 2.1, 2.2 - MEDIUM : ssl: memory leak of ocsp data at SSL_CTX_free() - 1.8, 2.0, 2.1, 2.2- MEDIUM : map/lua: Return an error if a map is loaded during runtime - 2.1, 2.2 - MINOR : arg: Fix leaks during arguments validation for fetches/converters - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IP mask in arg validation - 2.1, 2.2 - MINOR : ssl: fix memory leak at OCSP loading - 2.0, 2.1, 2.2 - MINOR : snapshots: leak of snapshots on deinit() - 1.8, 2.0, 2.1, 2.2- MINOR : stats: use strncmp() instead of memcmp() on health states - 2.2 - MINOR : ssl: ssl-skip-self-issued-ca requires >= 1.0.2 - 2.1, 2.2 - MINOR : lua: Duplicate map name to load it when a new Map object is created - 2.2 - MINOR : spoa-server: fix size_t format printing - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 1.8 - MINOR : dns: ignore trailing dot - 2.1, 2.2 - MINOR : converters: Store the sink in an arg pointer for debug() converter - 2.1, 2.2 - MINOR : lua: Duplicate lua strings in sample fetches/converters arg array -- 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: Bugfixes waiting for a release 2.2 (16), 2.1 (12), 2.0 (7), 1.8 (6)
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.2.2 was issued on 2020-07-31. There are currently 16 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-08-05 - 4 MEDIUM, first one merged on 2020-08-05 - 11 MINOR, first one merged on 2020-08-05 Thus the computed ideal release date for 2.2.3 would be 2020-08-19, which is in one week or less. Last release 2.1.8 was issued on 2020-07-31. There are currently 12 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2020-08-05 - 9 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which is in four weeks or less. Last release 2.0.17 was issued on 2020-07-31. There are currently 7 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-11 Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is in eight weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 6 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2020-08-05 - 4 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in eleven weeks or less. The current list of patches in the queue is: - 2.2 - MAJOR : dns: disabled servers through SRV records never recover - 1.8, 2.0, 2.1, 2.2- MEDIUM : map/lua: Return an error if a map is loaded during runtime - 2.0, 2.1, 2.2 - MEDIUM : mux-h1: Refresh H1 connection timeout after a synchronous send - 2.1, 2.2 - MEDIUM : ssl: memory leak of ocsp data at SSL_CTX_free() - 2.2 - MEDIUM : ssl: fix the ssl-skip-self-issued-ca option - 1.8, 2.0 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 2.0, 2.1, 2.2 - MINOR : snapshots: leak of snapshots on deinit() - 2.1, 2.2 - MINOR : lua: Duplicate map name to load it when a new Map object is created - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 2.1, 2.2 - MINOR : converters: Store the sink in an arg pointer for debug() converter - 2.2 - MINOR : spoa-server: fix size_t format printing - 1.8, 2.0, 2.1, 2.2- MINOR : lua: Check argument type to convert it to IP mask in arg validation - 1.8, 2.0, 2.1, 2.2- MINOR : stats: use strncmp() instead of memcmp() on health states - 2.1, 2.2 - MINOR : ssl: fix memory leak at OCSP loading - 2.1, 2.2 - MINOR : lua: Duplicate lua strings in sample fetches/converters arg array - 2.2 - MINOR : ssl: ssl-skip-self-issued-ca requires >= 1.0.2 - 1.8 - MINOR : dns: ignore trailing dot - 2.1, 2.2 - MINOR : arg: Fix leaks during arguments validation for fetches/converters -- 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: Bugfixes waiting for a release 1.8 (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 to this mail must be sent to the mailing list. Last release 1.8.26 was issued on 2020-08-03. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in twelve weeks or less. The current list of patches in the queue is: - 1.8 - MINOR : dns: ignore trailing dot -- 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: Bugfixes waiting for a release 2.2 (2), 2.1 (48), 2.0 (9)
NOR : debug: Don't dump the lua stack if it is not initialized - 2.0, 2.1 - MINOR : cfgparse: don't increment linenum on incomplete lines - 2.1 - MINOR : sample: Free str.area in smp_check_const_bool - 2.1 - MINOR : mux-h1: Don't read data from a pipe if the mux is unable to receive - 2.1 - MINOR : mworker/cli: fix the escaping in the master CLI - 2.1 - MINOR : mux-fcgi: Set conn state to RECORD_P when skipping the record padding - 2.1 - MINOR : backend: Remove CO_FL_SESS_IDLE if a client remains on the last server - 2.1 - MINOR : sample: Free str.area in smp_check_const_meth - 2.1 - MINOR : mux-fcgi: Set flags on the right stream field for empty FCGI_STDOUT - 2.0, 2.1 - MINOR : threads: Don't forget to init each thread toremove_lock. - 2.1 - MINOR : mux-fcgi: Handle empty STDERR record - 2.1 - MINOR : tcp-rules: tcp-response must check the buffer's fullness -- 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: Bugfixes waiting for a release 2.2 (18), 2.1 (42), 2.0 (3)
length check
before checking key names
- 2.1, 2.2 - MINOR : sample: Free str.area in
smp_check_const_bool
- 2.1 - MINOR : http_ana: clarify connection pointer
check on L7 retry
- 2.1 - MINOR : systemd: Wait for network to be online
- 2.1 - MINOR : spoe: correction of setting bits for
analyzer
- 2.1, 2.2 - MINOR : mux-fcgi: Handle empty STDERR record
- 2.1 - MINOR : mworker/cli: fix semicolon escaping in
master CLI
- 2.1 - MINOR : mux-h1: Disable splicing only if input
data was processed
- 2.0, 2.1 - MINOR : cfgparse: don't increment linenum on
incomplete lines
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
--
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: Bugfixes waiting for a release 2.1 (26), 2.0 (23)
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.1.7 was issued on 2020-06-09. There are currently 26 patches in
the queue cut down this way:
- 9 MEDIUM, first one merged on 2020-06-12
- 17 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which was
within the last week.
Last release 2.0.15 was issued on 2020-06-12. There are currently 23 patches
in the queue cut down this way:
- 1 MAJOR, first one merged on 2020-07-10
- 7 MEDIUM, first one merged on 2020-07-07
- 15 MINOR, first one merged on 2020-07-07
Thus the computed ideal release date for 2.0.16 would be 2020-08-07, which is
in four weeks or less.
The current list of patches in the queue is:
- 2.0 - MAJOR : stream: Mark the server address as
unset on new outgoing connection
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.0, 2.1 - MEDIUM : connection: Continue to recv data to a
pipe when the FD is not ready
- 2.0, 2.1 - MEDIUM : mux-h1: Subscribe rather than waking
up in h1_rcv_buf()
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.0, 2.1 - MEDIUM : mux-h1: Disable splicing for the
conn-stream if read0 is received
- 2.0, 2.1 - MEDIUM : fetch: Fix hdr_ip misparsing IPv4
addresses due to missing NUL
- 2.0, 2.1 - MEDIUM : ebtree: use a byte-per-byte memcmp()
to compare memory blocks
- 2.0 - MEDIUM : stream-int: Disable connection retries
on plain HTTP proxy mode
- 2.0, 2.1 - MEDIUM : pattern: Add a trailing \0 to match
strings only if possible
- 2.0, 2.1 - MINOR : tcp-rules: tcp-response must check the
buffer's fullness
- 2.0, 2.1 - MINOR : backend: Remove CO_FL_SESS_IDLE if a
client remains on the last server
- 2.0, 2.1 - MINOR : spoe: correction of setting bits for
analyzer
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
- 2.0, 2.1 - MINOR : mux-h1: Disable splicing only if input
data was processed
- 2.0, 2.1 - MINOR : proxy: always initialize the trash in
show servers state
- 2.0, 2.1 - MINOR : spoe: add missing key length check
before checking key names
- 2.0, 2.1 - MINOR : mworker/cli: fix the escaping in the
master CLI
- 2.0, 2.1 - MINOR : http_act: don't check capture id in
backend (2)
- 2.0, 2.1 - MINOR : proxy: fix dump_server_state()'s
misuse of the trash
- 2.0, 2.1 - MINOR : mux-h1: Don't read data from a pipe if
the mux is unable to receive
- 2.0, 2.1 - MINOR : mworker/cli: fix semicolon escaping in
master CLI
- 2.0, 2.1 - MINOR : mux-h1: Fix the splicing in TUNNEL mode
- 2.0, 2.1 - MINOR : systemd: Wait for network to be online
- 2.0, 2.1 - MINOR : http_ana: clarify connection pointer
check on L7 retry
- 2.1 - MINOR : http: make smp_fetch_body() report
that the contents may change
- 2.0, 2.1 - MINOR : cli: allow space escaping on the CLI
--
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: Bugfixes waiting for a release 2.1 (26)
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.1.7 was issued on 2020-06-09. There are currently 26 patches in
the queue cut down this way:
- 9 MEDIUM, first one merged on 2020-06-12
- 17 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which is in
one week or less.
The current list of patches in the queue is:
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.1 - MEDIUM : ebtree: use a byte-per-byte memcmp()
to compare memory blocks
- 2.1 - MEDIUM : fetch: Fix hdr_ip misparsing IPv4
addresses due to missing NUL
- 2.1 - MEDIUM : mux-h1: Disable splicing for the
conn-stream if read0 is received
- 2.1 - MEDIUM : mux-h1: Subscribe rather than waking
up in h1_rcv_buf()
- 2.1 - MEDIUM : connection: Continue to recv data to a
pipe when the FD is not ready
- 2.1 - MEDIUM : pattern: Add a trailing \0 to match
strings only if possible
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.1 - MINOR : proxy: fix dump_server_state()'s
misuse of the trash
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
- 2.1 - MINOR : spoe: add missing key length check
before checking key names
- 2.1 - MINOR : cli: allow space escaping on the CLI
- 2.1 - MINOR : mux-h1: Fix the splicing in TUNNEL mode
- 2.1 - MINOR : mworker/cli: fix the escaping in the
master CLI
- 2.1 - MINOR : spoe: correction of setting bits for
analyzer
- 2.1 - MINOR : http: make smp_fetch_body() report
that the contents may change
- 2.1 - MINOR : systemd: Wait for network to be online
- 2.1 - MINOR : backend: Remove CO_FL_SESS_IDLE if a
client remains on the last server
- 2.1 - MINOR : mux-h1: Don't read data from a pipe if
the mux is unable to receive
- 2.1 - MINOR : mux-h1: Disable splicing only if input
data was processed
- 2.1 - MINOR : proxy: always initialize the trash in
show servers state
- 2.1 - MINOR : tcp-rules: tcp-response must check the
buffer's fullness
- 2.1 - MINOR : mworker/cli: fix semicolon escaping in
master CLI
- 2.1 - MINOR : http_ana: clarify connection pointer
check on L7 retry
- 2.1 - MINOR : http_act: don't check capture id in
backend (2)
--
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: Bugfixes waiting for a release 2.1 (4)
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.1.7 was issued on 2020-06-09. There are currently 4 patches in
the queue cut down this way:
- 3 MEDIUM, first one merged on 2020-06-12
- 1 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which is in
two weeks or less.
The current list of patches in the queue is:
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
--
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: Bugfixes waiting for a release 2.1 (4)
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.1.7 was issued on 2020-06-09. There are currently 4 patches in
the queue cut down this way:
- 3 MEDIUM, first one merged on 2020-06-12
- 1 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which is in
three weeks or less.
The current list of patches in the queue is:
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
--
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: Bugfixes waiting for a release 2.1 (4)
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.1.7 was issued on 2020-06-09. There are currently 4 patches in
the queue cut down this way:
- 3 MEDIUM, first one merged on 2020-06-12
- 1 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which is in
four weeks or less.
The current list of patches in the queue is:
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
--
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: Bugfixes waiting for a release 2.0 (55)
- MINOR : config: Make use_backend and use-server post-parsing less obscur - 2.0 - MINOR : peers: fix internal/network key type mapping. - 2.0 - MINOR : cache: Don't needlessly test "cache" keyword in parse_cache_flt() - 2.0 - MINOR : ssl: default settings for ssl server options are not used - 2.0 - MINOR : sample: Set the correct type when a binary is converted to a string - 2.0 - MINOR : obj_type: Handle stream object in obj_base_ptr() function - 2.0 - MINOR : check: Update server address and port to execute an external check - 2.0 - MINOR : nameservers: fix error handling in parsing of resolv.conf - 2.0 - MINOR : cfgparse: Abort parsing the current line if an invalid \x sequence is encountered - 2.0 - MINOR : soft-stop: always wake up waiting threads on stopping - 2.0 - MINOR : tools: fix the i386 version of the div64_32 function - 2.0 - MINOR : checks: Remove a warning about http health checks - 2.0 - MINOR : lua: Add missing string length for lua sticktable lookup -- 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: Bugfixes waiting for a release 2.1 (1), 2.0 (48)
pecified
- 2.0 - MINOR : connection: make sure to correctly tag
local PROXY connections"
- 2.0 - MINOR : checks: Compute the right HTTP request
length for HTTP health checks
- 2.0 - MINOR : http-ana: fix NTLM response parsing
again
- 2.0 - MINOR : checks: Respect the no-check-ssl option
- 2.0 - MINOR : lua: Add missing string length for lua
sticktable lookup
- 2.0 - MINOR : threads: fix multiple use of argument
inside HA_ATOMIC_UPDATE_{MIN,MAX}()
- 2.0 - MINOR : sample: Set the correct type when a
binary is converted to a string
- 2.0 - MINOR : checks/server: use_ssl member must be
signed
- 2.0 - MINOR : pollers: remove uneeded free in global
init
--
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: Bugfixes waiting for a release 2.1 (52), 2.0 (45)
- MINOR : ssl: memleak of the struct cert_key_and_chain - 2.0, 2.1 - MINOR : debug: properly use long long instead of long for the thread ID - 2.0, 2.1 - MINOR : cache: Don't needlessly test "cache" keyword in parse_cache_flt() - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections" - 2.0, 2.1 - MINOR : http: make url_decode() optionally convert '+' to SP - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections - 2.0, 2.1 - MINOR : peers: Incomplete peers sections should be validated. - 2.0, 2.1 - MINOR : threads: fix multiple use of argument inside HA_ATOMIC_CAS() - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' - 2.0, 2.1 - MINOR : config: Make use_backend and use-server post-parsing less obscur - 2.0, 2.1 - MINOR : check: Update server address and port to execute an external check - 2.0, 2.1 - MINOR : server: Fix server_finalize_init() to avoid unused variable - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.0, 2.1 - MINOR : checks: chained expect will not properly wait for enough data - 2.1 - MINOR : mux-fcgi: Be sure to have a connection as session's origin to use it - 2.0, 2.1 - MINOR : http-ana: fix NTLM response parsing again - 2.0, 2.1 - MINOR : pools: use %u not %d to report pool stats in "show pools" -- 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: Bugfixes waiting for a release 2.1 (27), 2.0 (24)
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.1.4 was issued on 2020-04-02. There are currently 27 patches in
the queue cut down this way:
- 10 MEDIUM, first one merged on 2020-05-01
- 17 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which was
three weeks ago.
Last release 2.0.14 was issued on 2020-04-02. There are currently 24 patches
in the queue cut down this way:
- 12 MEDIUM, first one merged on 2020-05-07
- 12 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which was
three weeks ago.
The current list of patches in the queue is:
- 2.0, 2.1 - MEDIUM : server/checks: Init server check
during config validity check
- 2.0, 2.1 - MEDIUM : http: the "http_first_req" sample
fetch could crash without a steeam
- 2.0, 2.1 - MEDIUM : http: the "unique-id" sample fetch
could crash without a steeam
- 2.0, 2.1 - MEDIUM : shctx: bound the number of loops that
can happen around the lock
- 2.0, 2.1 - MEDIUM : capture: capture-req/capture-res
converters crash without a stream
- 2.0, 2.1 - MEDIUM : shctx: really check the lock's value
while waiting
- 2.0, 2.1 - MEDIUM : http-ana: Handle NTLM messages
correctly.
- 2.0, 2.1 - MEDIUM : listener: mark the thread as not stuck
inside the loop
- 2.0 - MEDIUM : backend: don't access a non-existing
mux from a previous connection
- 2.0, 2.1 - MEDIUM : sample: make the CPU and latency
sample fetches check for a stream
- 2.0 - MEDIUM : checks: Always initialize checks
before starting them
- 2.0, 2.1 - MEDIUM : capture: capture.{req,res}.* crash
without a stream
- 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum
shifting.
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections
- 2.0, 2.1 - MINOR : debug: properly use long long instead
of long for the thread ID
- 2.1 - MINOR : mux-fcgi: Be sure to have a connection
as session's origin to use it
- 2.0, 2.1 - MINOR : ssl: default settings for ssl server
options are not used
- 2.0, 2.1 - MINOR : tools: fix the i386 version of the
div64_32 function
- 2.0, 2.1 - MINOR : checks: chained expect will not
properly wait for enough data
- 2.0, 2.1 - MINOR : http: make url_decode() optionally
convert '+' to SP
- 2.0, 2.1 - MINOR : checks: Respect the no-check-ssl option
- 2.0, 2.1 - MINOR : checks/server: use_ssl member must be
signed
- 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert'
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections"
- 2.0, 2.1 - MINOR : connection: make sure to correctly tag
local PROXY connections"
- 2.0, 2.1 - MINOR : check: Update server address and port
to execute an external check
- 2.1 - MINOR : ssl: memleak of the struct
cert_key_and_chain
- 2.0, 2.1 - MINOR : obj_type: Handle stream object in
obj_base_ptr() function
- 2.0, 2.1 - MINOR : peers: Incomplete peers sections
should be validated.
--
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: Bugfixes waiting for a release 2.1 (27), 2.0 (24)
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.1.4 was issued on 2020-04-02. There are currently 27 patches in
the queue cut down this way:
- 10 MEDIUM, first one merged on 2020-05-01
- 17 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which was
two weeks ago.
Last release 2.0.14 was issued on 2020-04-02. There are currently 24 patches
in the queue cut down this way:
- 12 MEDIUM, first one merged on 2020-05-07
- 12 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which was
two weeks ago.
The current list of patches in the queue is:
- 2.0 - MEDIUM : backend: don't access a non-existing
mux from a previous connection
- 2.0, 2.1 - MEDIUM : server/checks: Init server check
during config validity check
- 2.0, 2.1 - MEDIUM : http: the "unique-id" sample fetch
could crash without a steeam
- 2.0, 2.1 - MEDIUM : shctx: really check the lock's value
while waiting
- 2.0, 2.1 - MEDIUM : capture: capture.{req,res}.* crash
without a stream
- 2.0, 2.1 - MEDIUM : http-ana: Handle NTLM messages
correctly.
- 2.0, 2.1 - MEDIUM : capture: capture-req/capture-res
converters crash without a stream
- 2.0, 2.1 - MEDIUM : listener: mark the thread as not stuck
inside the loop
- 2.0, 2.1 - MEDIUM : sample: make the CPU and latency
sample fetches check for a stream
- 2.0 - MEDIUM : checks: Always initialize checks
before starting them
- 2.0, 2.1 - MEDIUM : shctx: bound the number of loops that
can happen around the lock
- 2.0, 2.1 - MEDIUM : http: the "http_first_req" sample
fetch could crash without a steeam
- 2.0, 2.1 - MINOR : checks: chained expect will not
properly wait for enough data
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections"
- 2.0, 2.1 - MINOR : ssl: default settings for ssl server
options are not used
- 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum
shifting.
- 2.0, 2.1 - MINOR : checks: Respect the no-check-ssl option
- 2.0, 2.1 - MINOR : http: make url_decode() optionally
convert '+' to SP
- 2.1 - MINOR : ssl: memleak of the struct
cert_key_and_chain
- 2.0, 2.1 - MINOR : checks/server: use_ssl member must be
signed
- 2.0, 2.1 - MINOR : connection: make sure to correctly tag
local PROXY connections"
- 2.0, 2.1 - MINOR : check: Update server address and port
to execute an external check
- 2.0, 2.1 - MINOR : tools: fix the i386 version of the
div64_32 function
- 2.0, 2.1 - MINOR : peers: Incomplete peers sections
should be validated.
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections
- 2.0, 2.1 - MINOR : obj_type: Handle stream object in
obj_base_ptr() function
- 2.1 - MINOR : mux-fcgi: Be sure to have a connection
as session's origin to use it
- 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert'
- 2.0, 2.1 - MINOR : debug: properly use long long instead
of long for the thread ID
--
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: Bugfixes waiting for a release 2.1 (24), 2.0 (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 to this mail must be
sent to the mailing list.
Last release 2.1.4 was issued on 2020-04-02. There are currently 24 patches in
the queue cut down this way:
- 10 MEDIUM, first one merged on 2020-05-01
- 14 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which was
one week ago.
Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in
the queue cut down this way:
- 1 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which was
one week ago.
The current list of patches in the queue is:
- 2.1 - MEDIUM : shctx: really check the lock's value
while waiting
- 2.1 - MEDIUM : capture: capture.{req,res}.* crash
without a stream
- 2.1 - MEDIUM : http-ana: Handle NTLM messages
correctly.
- 2.1 - MEDIUM : listener: mark the thread as not stuck
inside the loop
- 2.1 - MEDIUM : http: the "unique-id" sample fetch
could crash without a steeam
- 2.1 - MEDIUM : server/checks: Init server check
during config validity check
- 2.1 - MEDIUM : http: the "http_first_req" sample
fetch could crash without a steeam
- 2.1 - MEDIUM : sample: make the CPU and latency
sample fetches check for a stream
- 2.1 - MEDIUM : shctx: bound the number of loops that
can happen around the lock
- 2.1 - MEDIUM : capture: capture-req/capture-res
converters crash without a stream
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections
- 2.1 - MINOR : ssl: default settings for ssl server
options are not used
- 2.1 - MINOR : mux-fcgi: Be sure to have a connection
as session's origin to use it
- 2.1 - MINOR : tools: fix the i386 version of the
div64_32 function
- 2.1 - MINOR : obj_type: Handle stream object in
obj_base_ptr() function
- 2.1 - MINOR : checks: Respect the no-check-ssl option
- 2.1 - MINOR : debug: properly use long long instead
of long for the thread ID
- 2.1 - MINOR : peers: Incomplete peers sections
should be validated.
- 2.1 - MINOR : checks: chained expect will not
properly wait for enough data
- 2.1 - MINOR : http: make url_decode() optionally
convert '+' to SP
- 2.1 - MINOR : ssl: memleak of the struct
cert_key_and_chain
- 2.1 - MINOR : check: Update server address and port
to execute an external check
- 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert'
- 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum
shifting.
--
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: Bugfixes waiting for a release 2.1 (4), 2.0 (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 to this mail must be sent to the mailing list. Last release 2.1.4 was issued on 2020-04-02. There are currently 4 patches in the queue cut down this way: - 4 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which was within the last week. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which was within the last week. The current list of patches in the queue is: - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.1 - MINOR : ssl: memleak of the struct cert_key_and_chain - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections -- 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: Bugfixes waiting for a release 2.1 (4), 2.0 (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 to this mail must be sent to the mailing list. Last release 2.1.4 was issued on 2020-04-02. There are currently 4 patches in the queue cut down this way: - 4 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which is in one week or less. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which is in one week or less. The current list of patches in the queue is: - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.1 - MINOR : ssl: memleak of the struct cert_key_and_chain - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' -- 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: Bugfixes waiting for a release 2.1 (4), 2.0 (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 to this mail must be sent to the mailing list. Last release 2.1.4 was issued on 2020-04-02. There are currently 4 patches in the queue cut down this way: - 4 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which is in two weeks or less. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which is in two weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections - 2.1 - MINOR : ssl: memleak of the struct cert_key_and_chain - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' -- 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: Bugfixes waiting for a release 2.1 (1), 2.0 (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 to this mail must be sent to the mailing list. Last release 2.1.4 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which is in three weeks or less. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which is in three weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. -- 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: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
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.1.3 was issued on 2020-02-12. There are currently 21 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 13 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which was two weeks ago. Last release 2.0.13 was issued on 2020-02-13. There are currently 16 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 9 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which was two weeks ago. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : http-ana: Always abort the request when a tarpit is triggered - 2.1 - MAJOR : list: fix invalid element address calculation - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when calling the destroy method. - 2.0, 2.1 - MEDIUM : ssl: fix several bad pointer aliases in a few sample fetch functions - 2.0, 2.1 - MEDIUM : shctx: make sure to keep all blocks aligned - 2.0, 2.1 - MEDIUM : ebtree: don't set attribute packed without unaligned access support - 2.0, 2.1 - MEDIUM : random: implement a thread-safe and process-safe PRNG - 2.0, 2.1 - MEDIUM : random: initialize the random pool a bit better - 2.0, 2.1 - MINOR : dns: ignore trailing dot - 2.0, 2.1 - MINOR : namespace: avoid closing fd when socket failed in my_socketat - 2.0, 2.1 - MINOR : sample: fix the json converter's endian-sensitivity - 2.1 - MINOR : h2: reject again empty :path pseudo-headers - 2.0, 2.1 - MINOR : connection: make sure to correctly tag local PROXY connections - 2.1 - MINOR : http-htx: Don't return error if authority is updated without changes - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri should be case-sensitive - 2.0, 2.1 - MINOR : checks/threads: use ha_random() and not rand() - 2.0, 2.1 - MINOR : filters: Count HTTP headers as filtered data but don't forward them - 2.1 - MINOR : mux-fcgi: Forbid special characters when matching PATH_INFO param - 2.1 - MINOR : http-htx: Do case-insensive comparisons on Host header name - 2.0, 2.1 - MINOR : sample: Make sure to return stable IDs in the unique-id fetch - 2.0, 2.1 - MINOR : http: http-request replace-path duplicates the query string -- 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: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
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.1.3 was issued on 2020-02-12. There are currently 21 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 13 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which was one week ago. Last release 2.0.13 was issued on 2020-02-13. There are currently 16 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 9 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which was one week ago. The current list of patches in the queue is: - 2.1 - MAJOR : list: fix invalid element address calculation - 2.0, 2.1 - MAJOR : http-ana: Always abort the request when a tarpit is triggered - 2.0, 2.1 - MEDIUM : shctx: make sure to keep all blocks aligned - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when calling the destroy method. - 2.0, 2.1 - MEDIUM : ebtree: don't set attribute packed without unaligned access support - 2.0, 2.1 - MEDIUM : random: implement a thread-safe and process-safe PRNG - 2.0, 2.1 - MEDIUM : random: initialize the random pool a bit better - 2.0, 2.1 - MEDIUM : ssl: fix several bad pointer aliases in a few sample fetch functions - 2.0, 2.1 - MINOR : connection: make sure to correctly tag local PROXY connections - 2.1 - MINOR : http-htx: Don't return error if authority is updated without changes - 2.0, 2.1 - MINOR : checks/threads: use ha_random() and not rand() - 2.0, 2.1 - MINOR : sample: Make sure to return stable IDs in the unique-id fetch - 2.1 - MINOR : mux-fcgi: Forbid special characters when matching PATH_INFO param - 2.0, 2.1 - MINOR : dns: ignore trailing dot - 2.0, 2.1 - MINOR : filters: Count HTTP headers as filtered data but don't forward them - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri should be case-sensitive - 2.1 - MINOR : http-htx: Do case-insensive comparisons on Host header name - 2.0, 2.1 - MINOR : namespace: avoid closing fd when socket failed in my_socketat - 2.1 - MINOR : h2: reject again empty :path pseudo-headers - 2.0, 2.1 - MINOR : sample: fix the json converter's endian-sensitivity - 2.0, 2.1 - MINOR : http: http-request replace-path duplicates the query string -- 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: Bugfixes waiting for a release 2.1 (17), 2.0 (13)
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.1.3 was issued on 2020-02-12. There are currently 17 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 4 MEDIUM, first one merged on 2020-02-21 - 12 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which was within the last week. Last release 2.0.13 was issued on 2020-02-13. There are currently 13 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 4 MEDIUM, first one merged on 2020-02-21 - 8 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which was within the last week. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : http-ana: Always abort the request when a tarpit is triggered - 2.0, 2.1 - MEDIUM : shctx: make sure to keep all blocks aligned - 2.0, 2.1 - MEDIUM : ebtree: don't set attribute packed without unaligned access support - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when calling the destroy method. - 2.0, 2.1 - MEDIUM : ssl: fix several bad pointer aliases in a few sample fetch functions - 2.1 - MINOR : http-htx: Don't return error if authority is updated without changes - 2.0, 2.1 - MINOR : dns: ignore trailing dot - 2.0, 2.1 - MINOR : filters: Count HTTP headers as filtered data but don't forward them - 2.0, 2.1 - MINOR : sample: Make sure to return stable IDs in the unique-id fetch - 2.1 - MINOR : h2: reject again empty :path pseudo-headers - 2.0, 2.1 - MINOR : sample: fix the json converter's endian-sensitivity - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri should be case-sensitive - 2.0, 2.1 - MINOR : http: http-request replace-path duplicates the query string - 2.1 - MINOR : mux-fcgi: Forbid special characters when matching PATH_INFO param - 2.1 - MINOR : http-htx: Do case-insensive comparisons on Host header name - 2.0, 2.1 - MINOR : connection: make sure to correctly tag local PROXY connections - 2.0, 2.1 - MINOR : namespace: avoid closing fd when socket failed in my_socketat -- 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: Bugfixes waiting for a release 2.1 (17), 2.0 (13)
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.1.3 was issued on 2020-02-12. There are currently 17 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 4 MEDIUM, first one merged on 2020-02-21 - 12 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which is in one week or less. Last release 2.0.13 was issued on 2020-02-13. There are currently 13 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 4 MEDIUM, first one merged on 2020-02-21 - 8 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which is in one week or less. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : http-ana: Always abort the request when a tarpit is triggered - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when calling the destroy method. - 2.0, 2.1 - MEDIUM : shctx: make sure to keep all blocks aligned - 2.0, 2.1 - MEDIUM : ebtree: don't set attribute packed without unaligned access support - 2.0, 2.1 - MEDIUM : ssl: fix several bad pointer aliases in a few sample fetch functions - 2.0, 2.1 - MINOR : http: http-request replace-path duplicates the query string - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri should be case-sensitive - 2.0, 2.1 - MINOR : sample: Make sure to return stable IDs in the unique-id fetch - 2.0, 2.1 - MINOR : namespace: avoid closing fd when socket failed in my_socketat - 2.0, 2.1 - MINOR : sample: fix the json converter's endian-sensitivity - 2.1 - MINOR : mux-fcgi: Forbid special characters when matching PATH_INFO param - 2.1 - MINOR : http-htx: Don't return error if authority is updated without changes - 2.0, 2.1 - MINOR : filters: Count HTTP headers as filtered data but don't forward them - 2.1 - MINOR : http-htx: Do case-insensive comparisons on Host header name - 2.0, 2.1 - MINOR : dns: ignore trailing dot - 2.0, 2.1 - MINOR : connection: make sure to correctly tag local PROXY connections - 2.1 - MINOR : h2: reject again empty :path pseudo-headers -- 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: Bugfixes waiting for a release 2.1 (7), 2.0 (5)
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.1.3 was issued on 2020-02-12. There are currently 7 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 1 MEDIUM, first one merged on 2020-02-21 - 5 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which is in two weeks or less. Last release 2.0.13 was issued on 2020-02-13. There are currently 5 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 1 MEDIUM, first one merged on 2020-02-21 - 3 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which is in two weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : http-ana: Always abort the request when a tarpit is triggered - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when calling the destroy method. - 2.0, 2.1 - MINOR : filters: Count HTTP headers as filtered data but don't forward them - 2.0, 2.1 - MINOR : namespace: avoid closing fd when socket failed in my_socketat - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri should be case-sensitive - 2.1 - MINOR : http-htx: Don't return error if authority is updated without changes - 2.1 - MINOR : mux-fcgi: Forbid special characters when matching PATH_INFO param --- 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: 31 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.23 was issued on 2019/11/25. There are currently 31 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 9 MEDIUM, first one merged on 2019/12/05 - 20 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was six weeks ago. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : pipe: fix a use-after-free in case of pipe creation error - MEDIUM : mworker: remain in mworker mode during reload - MINOR : sample: always check converters' arguments - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : listener: do not immediately resume on transient error - MINOR : stream: don't mistake match rules for store-request rules - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : dns: allow srv record weight set to 0 - MINOR : listener: fix off-by-one in state name check - MINOR : server: make "agent-addr" work on default-server line - MINOR : connection: fix ip6 dst_port copy in make_proxy_line_v2 - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : log: fix minor resource leaks on logformat error path - MINOR : listener: also clear the error flag on a paused listener - MINOR : http_act: don't check capture id in backend - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : pattern: handle errors from fgets when trying to load patterns --- 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: 62 bug fixes in queue for next release - 1.9
record weight set to 0 - MINOR : channel: inject output data at the end of output - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : http-rules: Remove buggy deinit functions for HTTP rules --- 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: 41 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.12 was issued on 2019/12/21. There are currently 41 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020/01/20 - 17 MEDIUM, first one merged on 2020/01/09 - 22 MINOR, first one merged on 2020/01/09 Thus the computed ideal release date for 2.0.13 would be 2020/02/03, which was one week ago. The current list of patches in the queue is: - MAJOR : memory: Don't forget to unlock the rwlock if the pool is empty. - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : pipe: fix a use-after-free in case of pipe creation error - MEDIUM : memory: Add a rwlock before freeing memory. - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : memory_pool: Update the seq number in pool_flush(). - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : ssl: Don't forget to free ctx->ssl on failure. - MEDIUM : connections: Don't forget to unlock when killing a connection. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : connection: add a mux flag to indicate splice usability - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : ssl: we may only ignore the first 64 errors - MINOR : checks: refine which errno values are really errors. - MINOR : connection: fix ip6 dst_port copy in make_proxy_line_v2 - MINOR : channel: inject output data at the end of output - MINOR : http_act: don't check capture id in backend - MINOR : cli/mworker: can't start haproxy with 2 programs - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : cache: Fix leak of cache name in error path - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : tcpchecks: fix the connect() flags regarding delayed ack - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : stktable: report the current proxy name in error messages - MINOR : proxy: Fix input data copy when an error is captured - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : 51d: Fix bug when HTX is enabled - MINOR : stream: don't mistake match rules for store-request rules - MINOR : dns: allow srv record weight set to 0 - MINOR : h1: Report the right error position when a header value is invalid --- 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: 54 bug fixes in queue for next release - 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 to this mail must be sent to the mailing list. Last release 2.1.2 was issued on 2019/12/21. There are currently 54 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020/01/20 - 20 MEDIUM, first one merged on 2020/01/09 - 32 MINOR, first one merged on 2020/01/07 Thus the computed ideal release date for 2.1.3 would be 2020/02/03, which was one week ago. The current list of patches in the queue is: - MAJOR : memory: Don't forget to unlock the rwlock if the pool is empty. - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : pipe: fix a use-after-free in case of pipe creation error - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : ssl/cli: 'commit ssl cert' wrong SSL_CTX init - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : ssl: Don't forget to free ctx->ssl on failure. - MEDIUM : memory: Add a rwlock before freeing memory. - MEDIUM : netscaler: Don't forget to allocate storage for conn->src/dst. - MEDIUM : connections: Don't forget to unlock when killing a connection. - MEDIUM : connection: add a mux flag to indicate splice usability - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : memory_pool: Update the seq number in pool_flush(). - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : tasks: Use the MT macros in tasklet_free(). - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MINOR : h1: Report the right error position when a header value is invalid - MINOR : channel: inject output data at the end of output - MINOR : ssl: we may only ignore the first 64 errors - MINOR : ssl/cli: free the previous ckch content once a PEM is loaded - MINOR : 51d: Fix bug when HTX is enabled - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : proxy: Fix input data copy when an error is captured - MINOR : ssl: increment issuer refcount if in chain - MINOR : stream: don't mistake match rules for store-request rules - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : connection: fix ip6 dst_port copy in make_proxy_line_v2 - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : http_act: don't check capture id in backend - MINOR : ssl: ssl_sock_load_issuer_file_into_ckch memory leak - MINOR : cli/mworker: can't start haproxy with 2 programs - MINOR : ssl/cli: ocsp_issuer must be set w/ "set ssl cert" - MINOR : ssl: ssl_sock_load_ocsp_response_from_file memory leak - MINOR : ssl: clear the SSL errors on DH loading failure - MINOR : tcpchecks: fix the connect() flags regarding delayed ack - MINOR : stktable: report the current proxy name in error messages - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : checks: refine which errno values are really errors. - MINOR : ssl: ssl_sock_load_sctl_from_file memory leak - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : ssl: ssl_sock_load_pem_into_ckch is not consistent - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : ssl: typo in previous patch - MINOR : ssl: Possible memleak when allowing the 0RTT data buffer. - MINOR : ssl: memory leak w/ the ocsp_issuer - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : cache: Fix leak of cache name in error path --- 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: 56 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.13 was issued on 2019/11/25. There are currently 56 patches in the queue cut down this way: - 3 MAJOR, first one merged on 2019/12/10 - 19 MEDIUM, first one merged on 2019/12/05 - 34 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which was six weeks ago. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MAJOR : task: add a new TASK_SHARED_WQ flag to fix foreing requeuing - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : fd/threads: fix a concurrency issue between add and rm on the same fd - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : stream: address a very rare unhandled connection issue - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : h1: Report the right error position when a header value is invalid - MINOR : stream: init variables when the list is empty - MINOR : listener: fix off-by-one in state name check - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : channel: inject output data at the end of output - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : listener: do not immediately resume on transient error - MINOR : listener: also clear the error flag on a paused listener - MINOR : cache: Fix leak of cache name in error path - MINOR : http_act: don't check capture id in backend - MINOR : sample: always check converters' arguments - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : proxy: Fix input data copy when an error is captured - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : ssl: openssl-compat: Fix getm_ defines - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : dns: allow srv record weight set to 0 - MINOR : 51d: Fix bug when HTX is enabled - MINOR : server: make "agent-addr" work on default-server line - MINOR : checks: refine which errno values are really errors. - MINOR : tasks: only requeue a task if it was already in the queue - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : log: fix minor resource leaks on logformat error path - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : stream: don't mistake match rules for store-request rules - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : ssl: openssl-compat: 1.9 uses OPENSSL_VERSION, not HA_OPENSSL_VERSION --- 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 so
stable-bot: WARNING: 29 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.23 was issued on 2019/11/25. There are currently 29 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 8 MEDIUM, first one merged on 2019/12/05 - 19 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was five weeks ago. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : sample: always check converters' arguments - MINOR : dns: allow srv record weight set to 0 - MINOR : listener: also clear the error flag on a paused listener - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener: do not immediately resume on transient error - MINOR : server: make "agent-addr" work on default-server line - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : stream: don't mistake match rules for store-request rules - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : listener: fix off-by-one in state name check - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : http_act: don't check capture id in backend - MINOR : log: fix minor resource leaks on logformat error path - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 --- 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: 44 bug fixes in queue for next release - 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 to this mail must be sent to the mailing list. Last release 2.1.2 was issued on 2019/12/21. There are currently 44 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020/01/20 - 15 MEDIUM, first one merged on 2020/01/09 - 28 MINOR, first one merged on 2020/01/07 Thus the computed ideal release date for 2.1.3 would be 2020/02/03, which was within the last week. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : netscaler: Don't forget to allocate storage for conn->src/dst. - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : tasks: Use the MT macros in tasklet_free(). - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : connection: add a mux flag to indicate splice usability - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : ssl: Don't forget to free ctx->ssl on failure. - MINOR : checks: refine which errno values are really errors. - MINOR : ssl/cli: ocsp_issuer must be set w/ "set ssl cert" - MINOR : ssl: ssl_sock_load_issuer_file_into_ckch memory leak - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : 51d: Fix bug when HTX is enabled - MINOR : http_act: don't check capture id in backend - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : channel: inject output data at the end of output - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : tcpchecks: fix the connect() flags regarding delayed ack - MINOR : h1: Report the right error position when a header value is invalid - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : ssl/cli: free the previous ckch content once a PEM is loaded - MINOR : ssl: ssl_sock_load_pem_into_ckch is not consistent - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : ssl: ssl_sock_load_sctl_from_file memory leak - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : stream: don't mistake match rules for store-request rules - MINOR : stktable: report the current proxy name in error messages - MINOR : ssl: increment issuer refcount if in chain - MINOR : proxy: Fix input data copy when an error is captured - MINOR : ssl: ssl_sock_load_ocsp_response_from_file memory leak - MINOR : ssl: memory leak w/ the ocsp_issuer - MINOR : ssl: typo in previous patch - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : cache: Fix leak of cache name in error path - MINOR : cli/mworker: can't start haproxy with 2 programs --- 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: 32 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.12 was issued on 2019/12/21. There are currently 32 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020/01/20 - 12 MEDIUM, first one merged on 2020/01/09 - 19 MINOR, first one merged on 2020/01/09 Thus the computed ideal release date for 2.0.13 would be 2020/02/03, which was within the last week. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MEDIUM : connection: add a mux flag to indicate splice usability - MINOR : checks: refine which errno values are really errors. - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : stktable: report the current proxy name in error messages - MINOR : cli/mworker: can't start haproxy with 2 programs - MINOR : proxy: Fix input data copy when an error is captured - MINOR : cache: Fix leak of cache name in error path - MINOR : http_act: don't check capture id in backend - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : channel: inject output data at the end of output - MINOR : dns: allow srv record weight set to 0 - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : 51d: Fix bug when HTX is enabled - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : h1: Report the right error position when a header value is invalid - MINOR : stream: don't mistake match rules for store-request rules --- 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: 44 bug fixes in queue for next release - 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 to this mail must be sent to the mailing list. Last release 2.1.2 was issued on 2019/12/21. There are currently 44 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020/01/20 - 15 MEDIUM, first one merged on 2020/01/09 - 28 MINOR, first one merged on 2020/01/07 Thus the computed ideal release date for 2.1.3 would be 2020/02/03, which is in one week or less. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : ssl: Don't forget to free ctx->ssl on failure. - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : connection: add a mux flag to indicate splice usability - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : tasks: Use the MT macros in tasklet_free(). - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : netscaler: Don't forget to allocate storage for conn->src/dst. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MINOR : ssl: ssl_sock_load_issuer_file_into_ckch memory leak - MINOR : cache: Fix leak of cache name in error path - MINOR : ssl: increment issuer refcount if in chain - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : proxy: Fix input data copy when an error is captured - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : cli/mworker: can't start haproxy with 2 programs - MINOR : ssl: typo in previous patch - MINOR : h1: Report the right error position when a header value is invalid - MINOR : ssl/cli: ocsp_issuer must be set w/ "set ssl cert" - MINOR : ssl: ssl_sock_load_sctl_from_file memory leak - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : channel: inject output data at the end of output - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : stream: don't mistake match rules for store-request rules - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : ssl: ssl_sock_load_ocsp_response_from_file memory leak - MINOR : checks: refine which errno values are really errors. - MINOR : ssl/cli: free the previous ckch content once a PEM is loaded - MINOR : ssl: ssl_sock_load_pem_into_ckch is not consistent - MINOR : tcpchecks: fix the connect() flags regarding delayed ack - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : 51d: Fix bug when HTX is enabled - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : http_act: don't check capture id in backend - MINOR : stktable: report the current proxy name in error messages - MINOR : ssl: memory leak w/ the ocsp_issuer --- 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: 29 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.23 was issued on 2019/11/25. There are currently 29 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 8 MEDIUM, first one merged on 2019/12/05 - 19 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was four weeks ago. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mworker: remain in mworker mode during reload - MINOR : sample: always check converters' arguments - MINOR : listener: do not immediately resume on transient error - MINOR : listener: also clear the error flag on a paused listener - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : log: fix minor resource leaks on logformat error path - MINOR : http_act: don't check capture id in backend - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : stream: don't mistake match rules for store-request rules - MINOR : listener: fix off-by-one in state name check - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : server: make "agent-addr" work on default-server line - MINOR : dns: allow srv record weight set to 0 --- 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: 56 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.13 was issued on 2019/11/25. There are currently 56 patches in the queue cut down this way: - 3 MAJOR, first one merged on 2019/12/10 - 19 MEDIUM, first one merged on 2019/12/05 - 34 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which was five weeks ago. The current list of patches in the queue is: - MAJOR : task: add a new TASK_SHARED_WQ flag to fix foreing requeuing - MAJOR : hashes: fix the signedness of the hash inputs - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : stream: address a very rare unhandled connection issue - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : fd/threads: fix a concurrency issue between add and rm on the same fd - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : listener/thread: fix a race when pausing a listener - MINOR : h1: Report the right error position when a header value is invalid - MINOR : listener: do not immediately resume on transient error - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : sample: always check converters' arguments - MINOR : channel: inject output data at the end of output - MINOR : stream: don't mistake match rules for store-request rules - MINOR : http_act: don't check capture id in backend - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : tasks: only requeue a task if it was already in the queue - MINOR : ssl: openssl-compat: 1.9 uses OPENSSL_VERSION, not HA_OPENSSL_VERSION - MINOR : proxy: Fix input data copy when an error is captured - MINOR : stream: init variables when the list is empty - MINOR : cache: Fix leak of cache name in error path - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : ssl: openssl-compat: Fix getm_ defines - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : log: fix minor resource leaks on logformat error path - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : server: make "agent-addr" work on default-server line - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : listener: fix off-by-one in state name check - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : checks: refine which errno values are really errors. - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : listener: also clear the error flag on a paused listener - MINOR : dns: allow srv record weight set to 0 - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : 51d: Fix bug when HTX is enabled --- 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 su
stable-bot: WARNING: 32 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.12 was issued on 2019/12/21. There are currently 32 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020/01/20 - 12 MEDIUM, first one merged on 2020/01/09 - 19 MINOR, first one merged on 2020/01/09 Thus the computed ideal release date for 2.0.13 would be 2020/02/03, which is in one week or less. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : connection: add a mux flag to indicate splice usability - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : http_act: don't check capture id in backend - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : cli/mworker: can't start haproxy with 2 programs - MINOR : 51d: Fix bug when HTX is enabled - MINOR : stream: don't mistake match rules for store-request rules - MINOR : channel: inject output data at the end of output - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : checks: refine which errno values are really errors. - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : h1: Report the right error position when a header value is invalid - MINOR : stktable: report the current proxy name in error messages - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : cache: Fix leak of cache name in error path - MINOR : dns: allow srv record weight set to 0 - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : proxy: Fix input data copy when an error is captured - MINOR : http-rules: Remove buggy deinit functions for HTTP rules --- 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: 17 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.23 was issued on 2019/11/25. There are currently 17 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/12/10 - 5 MEDIUM, first one merged on 2019/12/05 - 11 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was three weeks ago. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : listener/thread: fix a race when pausing a listener - MINOR : server: make "agent-addr" work on default-server line - MINOR : listener: fix off-by-one in state name check - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : log: fix minor resource leaks on logformat error path - MINOR : listener: do not immediately resume on transient error - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : listener: also clear the error flag on a paused listener - MINOR : sample: always check converters' arguments --- 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: 9 bug fixes in queue for next release - 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 to this mail must be sent to the mailing list. Last release 2.1.2 was issued on 2019/12/21. There are currently 9 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020/01/09 - 5 MINOR, first one merged on 2020/01/07 Thus the computed ideal release date for 2.1.3 would be 2020/02/04, which is in three weeks or less. The current list of patches in the queue is: - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MINOR : channel: inject output data at the end of output - MINOR : h1: Report the right error position when a header value is invalid - MINOR : checks: refine which errno values are really errors. - MINOR : proxy: Fix input data copy when an error is captured - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached --- 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: 9 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.12 was issued on 2019/12/21. There are currently 9 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020/01/09 - 5 MINOR, first one merged on 2020/01/09 Thus the computed ideal release date for 2.0.13 would be 2020/02/06, which is in three weeks or less. The current list of patches in the queue is: - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : checks: refine which errno values are really errors. - MINOR : h1: Report the right error position when a header value is invalid - MINOR : channel: inject output data at the end of output - MINOR : proxy: Fix input data copy when an error is captured --- 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: 37 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.13 was issued on 2019/11/25. There are currently 37 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 13 MEDIUM, first one merged on 2019/12/05 - 22 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which was four weeks ago. The current list of patches in the queue is: - MAJOR : task: add a new TASK_SHARED_WQ flag to fix foreing requeuing - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : fd/threads: fix a concurrency issue between add and rm on the same fd - MEDIUM : stream: address a very rare unhandled connection issue - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MINOR : ssl: openssl-compat: Fix getm_ defines - MINOR : h1: Report the right error position when a header value is invalid - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : sample: always check converters' arguments - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : proxy: Fix input data copy when an error is captured - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : checks: refine which errno values are really errors. - MINOR : channel: inject output data at the end of output - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : server: make "agent-addr" work on default-server line - MINOR : listener: also clear the error flag on a paused listener - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : log: fix minor resource leaks on logformat error path - MINOR : stream: init variables when the list is empty - MINOR : listener: fix off-by-one in state name check - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : tasks: only requeue a task if it was already in the queue - MINOR : listener: do not immediately resume on transient error - MINOR : ssl: openssl-compat: 1.9 uses OPENSSL_VERSION, not HA_OPENSSL_VERSION --- 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: 17 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.23 was issued on 2019/11/25. There are currently 17 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/12/10 - 5 MEDIUM, first one merged on 2019/12/05 - 11 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was two weeks ago. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : listener/thread: fix a race when pausing a listener - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : sample: always check converters' arguments - MINOR : listener: fix off-by-one in state name check - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : listener: also clear the error flag on a paused listener - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : listener: do not immediately resume on transient error - MINOR : server: make "agent-addr" work on default-server line - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : log: fix minor resource leaks on logformat error path --- 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: 37 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.13 was issued on 2019/11/25. There are currently 37 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 13 MEDIUM, first one merged on 2019/12/05 - 22 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which was three weeks ago. The current list of patches in the queue is: - MAJOR : task: add a new TASK_SHARED_WQ flag to fix foreing requeuing - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : fd/threads: fix a concurrency issue between add and rm on the same fd - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : stream: address a very rare unhandled connection issue - MEDIUM : ssl: Don't set the max early data we can receive too early. - MINOR : stream: init variables when the list is empty - MINOR : h1: Report the right error position when a header value is invalid - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : ssl: openssl-compat: Fix getm_ defines - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : proxy: Fix input data copy when an error is captured - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : listener: fix off-by-one in state name check - MINOR : tasks: only requeue a task if it was already in the queue - MINOR : log: fix minor resource leaks on logformat error path - MINOR : checks: refine which errno values are really errors. - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : listener: do not immediately resume on transient error - MINOR : server: make "agent-addr" work on default-server line - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : ssl: openssl-compat: 1.9 uses OPENSSL_VERSION, not HA_OPENSSL_VERSION - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : channel: inject output data at the end of output - MINOR : sample: always check converters' arguments - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener: also clear the error flag on a paused listener - MINOR : http-htx: Don't make http_find_header() fail if the value is empty --- 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: INFO: 9 bug fixes in queue for next release - 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 to this mail must be sent to the mailing list. Last release 2.1.2 was issued on 2019/12/21. There are currently 9 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020/01/09 - 5 MINOR, first one merged on 2020/01/07 Thus the computed ideal release date for 2.1.3 would be 2020/02/04, which is in four weeks or less. The current list of patches in the queue is: - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : channel: inject output data at the end of output - MINOR : proxy: Fix input data copy when an error is captured - MINOR : checks: refine which errno values are really errors. - MINOR : h1: Report the right error position when a header value is invalid --- 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: INFO: 9 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.12 was issued on 2019/12/21. There are currently 9 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020/01/09 - 5 MINOR, first one merged on 2020/01/09 Thus the computed ideal release date for 2.0.13 would be 2020/02/06, which is in four weeks or less. The current list of patches in the queue is: - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : session: do not report a failure when rejecting a session - MINOR : channel: inject output data at the end of output - MINOR : proxy: Fix input data copy when an error is captured - MINOR : h1: Report the right error position when a header value is invalid - MINOR : checks: refine which errno values are really errors. - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached --- 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: 31 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.13 was issued on 2019/11/25. There are currently 31 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 11 MEDIUM, first one merged on 2019/12/05 - 18 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which was two weeks ago. The current list of patches in the queue is: - MAJOR : task: add a new TASK_SHARED_WQ flag to fix foreing requeuing - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : stream: address a very rare unhandled connection issue - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : fd/threads: fix a concurrency issue between add and rm on the same fd - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : kqueue: Make sure we report read events even when no data. - MINOR : listener: also clear the error flag on a paused listener - MINOR : sample: always check converters' arguments - MINOR : log: fix minor resource leaks on logformat error path - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : listener: do not immediately resume on transient error - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : listener: fix off-by-one in state name check - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : stream: init variables when the list is empty - MINOR : ssl: openssl-compat: 1.9 uses OPENSSL_VERSION, not HA_OPENSSL_VERSION - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : server: make "agent-addr" work on default-server line - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : ssl: openssl-compat: Fix getm_ defines - MINOR : tasks: only requeue a task if it was already in the queue --- 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: 17 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.23 was issued on 2019/11/25. There are currently 17 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/12/10 - 5 MEDIUM, first one merged on 2019/12/05 - 11 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was one week ago. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : listener/thread: fix a race when pausing a listener - MINOR : listener: fix off-by-one in state name check - MINOR : server: make "agent-addr" work on default-server line - MINOR : listener: do not immediately resume on transient error - MINOR : listener: also clear the error flag on a paused listener - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : sample: always check converters' arguments - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : log: fix minor resource leaks on logformat error path --- 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: 31 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.13 was issued on 2019/11/25. There are currently 31 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 11 MEDIUM, first one merged on 2019/12/05 - 18 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which was one week ago. The current list of patches in the queue is: - MAJOR : task: add a new TASK_SHARED_WQ flag to fix foreing requeuing - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : fd/threads: fix a concurrency issue between add and rm on the same fd - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : stream: address a very rare unhandled connection issue - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MINOR : tasks: only requeue a task if it was already in the queue - MINOR : server: make "agent-addr" work on default-server line - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : stream: init variables when the list is empty - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : ssl: openssl-compat: 1.9 uses OPENSSL_VERSION, not HA_OPENSSL_VERSION - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener: do not immediately resume on transient error - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : log: fix minor resource leaks on logformat error path - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : listener: also clear the error flag on a paused listener - MINOR : listener: fix off-by-one in state name check - MINOR : ssl: openssl-compat: Fix getm_ defines - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : sample: always check converters' arguments --- 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: 17 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.23 was issued on 2019/11/25. There are currently 17 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/12/10 - 5 MEDIUM, first one merged on 2019/12/05 - 11 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was within the last week. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MINOR : server: make "agent-addr" work on default-server line - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : listener: fix off-by-one in state name check - MINOR : listener: do not immediately resume on transient error - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : sample: always check converters' arguments - MINOR : log: fix minor resource leaks on logformat error path - MINOR : listener: also clear the error flag on a paused listener --- 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: 31 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.13 was issued on 2019/11/25. There are currently 31 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 11 MEDIUM, first one merged on 2019/12/05 - 18 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which was within the last week. The current list of patches in the queue is: - MAJOR : task: add a new TASK_SHARED_WQ flag to fix foreing requeuing - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : fd/threads: fix a concurrency issue between add and rm on the same fd - MEDIUM : stream: address a very rare unhandled connection issue - MINOR : stream: init variables when the list is empty - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : ssl: openssl-compat: 1.9 uses OPENSSL_VERSION, not HA_OPENSSL_VERSION - MINOR : tasks: only requeue a task if it was already in the queue - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : listener: do not immediately resume on transient error - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : listener: also clear the error flag on a paused listener - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener: fix off-by-one in state name check - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : server: make "agent-addr" work on default-server line - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : ssl: openssl-compat: Fix getm_ defines - MINOR : sample: always check converters' arguments - MINOR : log: fix minor resource leaks on logformat error path --- 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: 17 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.23 was issued on 2019/11/25. There are currently 17 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/12/10 - 5 MEDIUM, first one merged on 2019/12/05 - 11 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which is in one week or less. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/thread: fix a race when pausing a listener - MINOR : listener: do not immediately resume on transient error - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : listener: fix off-by-one in state name check - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : log: fix minor resource leaks on logformat error path - MINOR : sample: always check converters' arguments - MINOR : server: make "agent-addr" work on default-server line - MINOR : listener: also clear the error flag on a paused listener - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state --- 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: 24 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.13 was issued on 2019/11/25. There are currently 24 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/12/10 - 9 MEDIUM, first one merged on 2019/12/05 - 14 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which is in one week or less. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : stream: address a very rare unhandled connection issue - MINOR : listener: do not immediately resume on transient error - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : server: make "agent-addr" work on default-server line - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : tasks: only requeue a task if it was already in the queue - MINOR : listener: fix off-by-one in state name check - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : stream: init variables when the list is empty - MINOR : log: fix minor resource leaks on logformat error path - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : listener: also clear the error flag on a paused listener - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers --- 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: 14 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.23 was issued on 2019/11/25. There are currently 14 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/12/10 - 4 MEDIUM, first one merged on 2019/12/05 - 9 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which is in two weeks or less. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : kqueue: Make sure we report read events even when no data. - MINOR : listener: fix off-by-one in state name check - MINOR : server: make "agent-addr" work on default-server line - MINOR : listener: also clear the error flag on a paused listener - MINOR : log: fix minor resource leaks on logformat error path - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener: do not immediately resume on transient error - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 --- 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: 17 bug fixes in queue for next release - 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 to this mail must be sent to the mailing list. Last release 2.1.0 was issued on 2019/11/25. There are currently 17 patches in the queue cut down this way: - 5 MEDIUM, first one merged on 2019/12/05 - 12 MINOR, first one merged on 2019/11/27 Thus the computed ideal release date for 2.1.1 would be 2019/12/25, which is in three weeks or less. The current list of patches in the queue is: - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MINOR : ssl/cli: 'ssl cert' cmd only usable w/ admin rights - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : h1: Don't test the host header during response parsing - MINOR : ssl: fix SSL_CTX_set1_chain compatibility for openssl < 1.0.2 - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : fcgi-app: Make the directive pass-header case insensitive - MINOR : stream-int: avoid calling rcv_buf() when splicing is still possible - MINOR : ssl/cli: don't overwrite the filters variable - MINOR : contrib/prometheus-exporter: decode parameter and value only - MINOR : stats: Fix HTML output for the frontends heading - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 --- 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: INFO: 2 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.23 was issued on 2019/11/25. There are currently 2 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2019/12/05 - 1 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2020/01/02, which is in four weeks or less. The current list of patches in the queue is: - MEDIUM : listener/thread: fix a race when pausing a listener - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 --- 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: 11 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.13 was issued on 2019/11/25. There are currently 11 patches in the queue cut down this way: - 6 MEDIUM, first one merged on 2019/12/05 - 5 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which is in two weeks or less. The current list of patches in the queue is: - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : stream: address a very rare unhandled connection issue - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : stream: init variables when the list is empty --- 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: 13 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.10 was issued on 2019/11/25. There are currently 13 patches in the queue cut down this way: - 5 MEDIUM, first one merged on 2019/12/05 - 8 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 2.0.11 would be 2019/12/23, which is in two weeks or less. The current list of patches in the queue is: - MEDIUM : checks: Make sure we set the task affinity just before connecting. - MEDIUM : stream-int: don't subscribed for recv when we're trying to flush data - MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity(). - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending - MINOR : contrib/prometheus-exporter: decode parameter and value only - MINOR : mux-h1: Fix conditions to know whether or not we may receive data - MINOR : stream-int: avoid calling rcv_buf() when splicing is still possible - MINOR : stream: init variables when the list is empty - MINOR : contrib/prometheus-exporter: Use HTX errors and not legacy ones - MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN - MINOR : http-htx: Don't make http_find_header() fail if the value is empty - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 --- 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: 2 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.13 was issued on 2019/11/25. There are currently 2 patches in the queue cut down this way: - 2 MINOR, first one merged on 2019/11/25 Thus the computed ideal release date for 1.9.14 would be 2019/12/23, which is in three weeks or less. The current list of patches in the queue is: - MINOR : stream: init variables when the list is empty - MINOR : http-htx: Don't make http_find_header() fail if the value is empty --- 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.
