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.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 (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), 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 (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 (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 (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 (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.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: 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 (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 (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 (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 (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 (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 (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 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 (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 (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 (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 (52), 2.0 (45)
- 2.1 - 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 (1), 2.0 (48)
m when a
port or an addr is specified
- 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.0 (55)
- 2.0 - 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 (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.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
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 (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 (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.2 (18), 2.1 (42), 2.0 (3)
- MINOR : spoe: add missing key 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.2 (2), 2.1 (48), 2.0 (9)
2.2 - MINOR : 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 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 (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 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 (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 (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.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 (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.2 (11), 2.1 (34), 2.0 (26), 1.8 (11)
s: Replace path and 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 (11), 2.1 (36), 2.0 (26), 1.8 (12)
- MINOR : 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 (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 (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 (20), 2.1 (16), 2.0 (15), 1.8 (20)
dot - 2.0, 2.1, 2.2 - 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 (25), 2.1 (18), 2.0 (15), 1.8 (20)
connections on stopping - 2.2 - 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 (40), 2.1 (35), 2.0 (30), 1.8 (20)
seesion reset after collisions. - 2.2 - 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.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 (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 (11), 2.2 (20), 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.3.1 was issued on 2020-11-13. There are currently 11 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-11-24 - 5 MEDIUM, first one merged on 2020-11-18 - 4 MINOR, first one merged on 2020-11-18 Thus the computed ideal release date for 2.3.2 would be 2020-12-08, which is in two weeks or less. Last release 2.2.5 was issued on 2020-11-05. There are currently 20 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-11-13 - 4 MEDIUM, first one merged on 2020-11-13 - 14 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 one week or less. 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 three 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 three 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.0, 2.1, 2.2, 2.3- MAJOR : filters: Always keep all offsets up to date during data filtering - 2.3 - MAJOR : connection: reset conn->owner when detaching from session list - 2.0, 2.1, 2.2 - MEDIUM : peers: fix decoding of multi-byte length in stick-table messages - 2.2 - MEDIUM : check: reuse srv proto only if using same mode - 2.2, 2.3 - MEDIUM : http-ana: Don't eval http-after-response ruleset on empty messages - 2.3 - MEDIUM : ssl: error when no certificate are found - 2.3 - MEDIUM : ssl/crt-list: fix error when no file found - 2.3 - MEDIUM : ssl/crt-list: bundle support broken in crt-list - 2.0, 2.1, 2.2, 2.3- MEDIUM : filters: Forward all filtered data at the end of http filtering - 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 : http-fetch: Extract cookie value even when no cookie name - 2.2 - MINOR : tcpcheck: Don't warn on unused rules if check option is after - 2.0, 2.1, 2.2, 2.3- MINOR : http-ana: Don't wait for the body of CONNECT requests - 2.0, 2.1, 2.2 - MINOR : pattern: a sample marked as const could be written - 2.2 - MINOR : ssl: don't report 1024 bits DH param load error when it's higher - 2.2 - MINOR : ssl: double free w/ smp_fetch_ssl_x_chain_der() - 2.0, 2.1, 2.2 - MINOR : lua: set buffer size during map lookups - 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 : peers: Missing TX cache entries reset. - 2.2, 2.3 - MINOR : http_htx: Fix searching headers by substring - 2.2, 2.3 - MINOR : ssl: segv on startup when AKID but no keyid - 2.3 - MINOR : ssl/crt-list: load bundle in crt-list only if activated - 2.2 - MINOR : http-htx: Handle warnings when parsing http-error and http-errors - 2.0, 2.1, 2.2 - MINOR : peers: Do not ignore a protocol error for dictionary entries. -- 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.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.3 (23), 2.2 (17), 2.1 (26), 2.0 (24)
ors - 2.1 - 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.3 (23), 2.2 (17), 2.1 (26), 2.0 (24)
ed beyond the first one - 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)
2, 2.3- MINOR : 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)
ua-load doesn't 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 (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 (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.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.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.3 (23), 2.1 (19), 2.0 (15)
eers: Wrong "new_conn" 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.3 (41), 2.2 (38), 2.1 (50), 2.0 (43)
ssible cpus report 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 (4), 2.2 (1), 2.1 (55), 2.0 (45)
buf() - 2.0, 2.1 - 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.2 (10), 2.1 (55), 2.0 (45)
rt the change on ST_CONVDONE - 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 (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 (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 (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.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 (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.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 (10), 2.1 (44), 2.0 (26)
already forwarded - 2.1 - 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: NOTICE: 31 bug fixes in queue for next release
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.0 was issued on 2018/12/19. There are currently 31 patches in the queue cut down this way: - 6 MAJOR, first one merged on 2019/01/04 - 20 MEDIUM, first one merged on 2019/01/04 - 5 MINOR, first one merged on 2019/01/04 Thus the computed ideal release date for 1.9.1 would be 2019/01/18, which is in two weeks or less. The current list of patches in the queue is: - MAJOR : htx: Return the good block address after a defrag - MAJOR : servers: Use the list api correctly to avoid crashes. - MAJOR : stream-int: Update the stream expiration date in stream_int_notify() - MAJOR : sessions: Use an unlimited number of servers for the conn list. - MAJOR : servers: Correctly use LIST_ELEM(). - MAJOR : connections: Close the connection before freeing it. - MEDIUM : servers: Don't try to reuse connection if we switched server. - MEDIUM : mux_h2: Don't add to the idle list if we're full. - MEDIUM : proto-htx: Set SI_FL_NOHALF on server side when request is done - MEDIUM : server: Also copy "check-sni" for server templates. - MEDIUM : log: don't mark log FDs as non-blocking on terminals - MEDIUM : mux-h1: make HTX chunking consistent with H2 - MEDIUM : tasks: Decrement tasks_run_queue in tasklet_free(). - MEDIUM : mux-h2: Don't forget to quit the send list on error reports - MEDIUM : servers: Flag the stream_interface on handshake error. - MEDIUM : h2: Don't forget to quit the sending_list if SUB_CALL_UNSUBSCRIBE. - MEDIUM : mux-h1: use per-direction flags to indicate transitions - MEDIUM : mux-h2: mark that we have too many CS once we have more than the max - MEDIUM : mux-h1: don't enforce chunked encoding on requests - MEDIUM : servers: Fail if we fail to allocate a conn_stream. - MEDIUM : mux-h2: don't needlessly wake up the demux on short frames - MEDIUM : mux-h1: Add a task to handle connection timeouts - MEDIUM : dns: overflowed dns name start position causing invalid dns error - MEDIUM : mux-h2: always restart reading if data are available - MEDIUM : dns: Don't prevent reading the last byte of the payload in dns_validate_response() - MEDIUM : cache: Be sure to end the forwarding when XFER length is unknown - MINOR : mux-h2: make empty HEADERS frame return a connection error - MINOR : htx: send the proper authenticate header when using http-request auth - MINOR : mux-h2: don't check the CS count in h2c_bck_handle_headers() - MINOR : compression/htx: Don't add the last block of data if it is empty - MINOR : compression/htx: Don't compress responses with unknown body length --- 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: 22 bug fixes in queue for next release
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.2 was issued on 2019/01/16. There are currently 22 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/01/26 - 8 MEDIUM, first one merged on 2019/01/21 - 13 MINOR, first one merged on 2019/01/21 Thus the computed ideal release date for 1.9.3 would be 2019/02/09, which is in two weeks or less. The current list of patches in the queue is: - MAJOR : mux-h2: don't destroy the stream on failed allocation in h2_snd_buf() - MEDIUM : mux-h2: properly abort on trailers decoding errors - MEDIUM : connections: Add the CO_FL_CONNECTED flag if a send succeeded. - MEDIUM : checks: fix recent regression on agent-check making it crash - MEDIUM : mux-h2/htx: Respect the channel's reserve - MEDIUM : servers: Make assign_tproxy_address work when ALPN is set. - MEDIUM : backend: never try to attach to a mux having no more stream available - MEDIUM : ssl: Fix handling of TLS 1.3 KeyUpdate messages - MEDIUM : backend: also remove from idle list muxes that have no more room - MINOR : mux-h2: refuse to allocate a stream with too high an ID - MINOR : server: don't always trust srv_check_health when loading a server state - MINOR : mux-h2: make it possible to set the error code on an already closed stream - MINOR : mux-h2: always check the stream ID limit in h2_avail_streams() - MINOR : mux-h1: Apply the reserve on the channel's buffer only - MINOR : hpack: return a compression error on invalid table size updates - MINOR : stream: take care of synchronous errors when trying to send - MINOR : mux-h2: headers-type frames in HREM are always a connection error - MINOR : mux-h2: CONTINUATION in closed state must always return GOAWAY - MINOR : proto-htx: Return an error if all headers cannot be received at once - MINOR : startup: certain goto paths in init_pollers fail to free - MINOR : mux-h1: avoid copying output over itself in zero-copy - MINOR : check: Wake the check task if the check is finished in wake_srv_chk() --- 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: 10 bug fixes in queue for next release
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.17 was issued on 2019/01/08. There are currently 10 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/01/28 - 3 MEDIUM, first one merged on 2019/01/28 - 6 MINOR, first one merged on 2019/01/28 Thus the computed ideal release date for 1.8.18 would be 2019/02/11, which is in one week or less. The current list of patches in the queue is: - MAJOR : cache: fix confusion between zero and uninitialized cache key - MEDIUM : ssl: missing allocation failure checks loading tls key file - MEDIUM : ssl: Fix handling of TLS 1.3 KeyUpdate messages - MEDIUM : ssl: Disable anti-replay protection and set max data with 0RTT. - MINOR : server: don't always trust srv_check_health when loading a server state - MINOR : check: Wake the check task if the check is finished in wake_srv_chk() - MINOR : stick_table: Prevent conn_cur from underflowing - MINOR : backend: BE_LB_LKUP_CHTREE is a value, not a bit - MINOR : backend: don't use url_param_name as a hint for BE_LB_ALGO_PH - MINOR : backend: balance uri specific options were lost across defaults --- 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: 31 bug fixes in queue for next release
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.3 was issued on 2019/01/29. There are currently 31 patches in the queue cut down this way: - 24 MEDIUM, first one merged on 2019/02/01 - 7 MINOR, first one merged on 2019/02/01 Thus the computed ideal release date for 1.9.4 would be 2019/03/01, which is in four weeks or less. The current list of patches in the queue is: - MEDIUM : servers: Close the connection if we failed to install the mux. - MEDIUM : mux-h1: Don't add "transfer-encoding" if message-body is forbidden - MEDIUM : mux-h2: fix two half-closed to closed transitions - MEDIUM : peers: Handle mux creation failure. - MEDIUM : checks: Don't try to set ALPN if connection failed. - MEDIUM : h2: In h2_send(), stop the loop if we failed to alloc a buf. - MEDIUM : buffer: Make sure b_is_null handles buffers waiting for allocation. - MEDIUM : connections: Don't forget to remove CO_FL_SESS_IDLE. - MEDIUM : mux-h2: do not abort HEADERS frame before decoding them - MEDIUM : checks: Check that conn_install_mux succeeded. - MEDIUM : mux-h2: only close connection on request frames on closed streams - MEDIUM : mux-h2: wait for the mux buffer to be empty before closing the connection - MEDIUM : servers: Don't add an incomplete conn to the server idle list. - MEDIUM : servers: Only destroy a conn_stream we just allocated. - MEDIUM : htx: check the HTX compatibility in dynamic use-backend rules - MEDIUM : mux-h2: do not close the connection on aborted streams - MEDIUM : mux-h2: make sure never to send GOAWAY on too old streams - MEDIUM : backend: always release the previous connection into its own target srv_list - MEDIUM : mux-h2: wake up flow-controlled streams on initial window update - MEDIUM : mux-h2: always omit :scheme and :path for the CONNECT method - MEDIUM : mux-h2: properly consider the peer's advertised max-concurrent-streams - MEDIUM : stream: Don't forget to free s->unique_id in stream_free(). - MEDIUM : mux-h2: always set :authority on request output - MEDIUM : compression: Rewrite strong ETags - MINOR : mux-h2: always compare content-length to the sum of DATA frames - MINOR : stream: don't close the front connection when facing a backend error - MINOR : mux-h2: make sure response HEADERS are not received in other states than OPEN and HLOC - MINOR : server: fix logic flaw in idle connection list management - MINOR : deinit: tcp_rep.inspect_rules not deinit, add to deinit - MINOR : mux-h2: make sure request trailers on aborted streams don't break the connection - MINOR : backend: check srv_conn before dereferencing it --- 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: 42 bug fixes in queue for next release
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.4 was issued on 2019/02/06. There are currently 42 patches in the queue cut down this way: - 1 BUG, first one merged on 2019/02/10 - 6 MAJOR, first one merged on 2019/02/10 - 20 MEDIUM, first one merged on 2019/02/10 - 15 MINOR, first one merged on 2019/02/10 Thus the computed ideal release date for 1.9.5 would be 2019/02/24, which was two weeks ago. The current list of patches in the queue is: - BUG : 51d: In Hash Trie, multi header matching was affected by the header names stored globaly. - MAJOR : listener: Make sure the listener exist before using it. - MAJOR : cache/htx: Set the start-line offset when a cached object is served - MAJOR : mux-h2: fix race condition between close on both ends - MAJOR : spoe: Don't try to get agent config during SPOP healthcheck - MAJOR : fd/threads, task/threads: ensure all spin locks are unlocked - MAJOR : stream: avoid double free on unique_id - MEDIUM : htx: count the amount of copied data towards the final count - MEDIUM : logs: Only attempt to free startup_logs once. - MEDIUM : server: initialize the idle conns list after parsing the config - MEDIUM : server: initialize the orphaned conns lists and tasks at the end - MEDIUM : mux-h1: Report the right amount of data xferred in h1_rcv_buf() - MEDIUM : proto_htx: Fix functions applying regex filters on HTX messages - MEDIUM : h2/htx: verify that :path doesn't contain invalid chars - MEDIUM : cache: Get objects from the cache only for GET and HEAD requests - MEDIUM : h2/htx: Correctly handle interim responses when HTX is enabled - MEDIUM : proto_htx: Fix data size update if end of the cookie is removed - MEDIUM : http_fetch: fix the "base" and "base32" fetch methods in HTX mode - MEDIUM : servers: Add a per-thread counter of idle connections. - MEDIUM : listeners: Don't call fd_stop_recv() if fd_updt is NULL. - MEDIUM : 51d: fix possible segfault on deinit_51degrees() - MEDIUM : servers: Use atomic operations when handling curr_idle_conns. - MEDIUM : h2: advertise to servers that we don't support push - MEDIUM : mux-h2/htx: send an empty DATA frame on empty HTX trailers - MEDIUM : http_fetch: fix "req.body_len" and "req.body_size" fetch methods in HTX mode - MEDIUM : spoe: initialization depending on nbthread must be done last - MEDIUM : mux-h2/htx: Always set CS flags before exiting h2_rcv_buf() - MINOR : ssl: fix warning about ssl-min/max-ver support - MINOR : channel: Set CF_WROTE_DATA when outgoing data are skipped - MINOR : lua: initialize the correct idle conn lists for the SSL sockets - MINOR : checks: make external-checks restore the original rlim_fd_cur/max - MINOR : config: Reinforce validity check when a process number is parsed - MINOR : mux-h2: Don't add ":status" pseudo-header on trailers - MINOR : spoe: do not assume agent->rt is valid on exit - MINOR : mux-h1: Add "transfer-encoding" header on outgoing requests if needed - MINOR : listener: keep accept rate counters accurate under saturation - MINOR : mworker: be careful to restore the original rlim_fd_cur/max on reload - MINOR : proto-htx: Consider a XFER_LEN message as chunked by default - MINOR : mux-h1: verify the request's version before dropping connection: keep-alive - MINOR : init: never lower rlim_fd_max - MINOR : cache/htx: Return only the headers of cached objects to HEAD requests - MINOR : mux-h1: Always initilize h1m variable in h1_process_input() --- 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: 3 bug fixes in queue for next release
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.5 was issued on 2019/03/19. There are currently 3 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2019/03/21 Thus the computed ideal release date for 1.9.6 would be 2019/04/20, which is in four weeks or less. The current list of patches in the queue is: - MEDIUM : mux-h2: Don't bother keeping the h2s if detaching and nothing to send. - MEDIUM : mux-h2: Make sure we destroyed the h2s once shutr/shutw is done. - MEDIUM : mux-h2: Use the right list in h2_stop_senders(). --- 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: 7 bug fixes in queue for next release
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.19 was issued on 2019/02/11. There are currently 7 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/03/11 - 3 MEDIUM, first one merged on 2019/03/11 - 2 MINOR, first one merged on 2019/03/11 Thus the computed ideal release date for 1.8.20 would be 2019/03/25, which was within the last week. The current list of patches in the queue is: - MAJOR : spoe: Fix initialization of thread-dependent fields - MAJOR : listener: Make sure the listener exist before using it. - MEDIUM : 51d: fix possible segfault on deinit_51degrees() - MEDIUM : threads/fd: do not forget to take into account epoll_fd/pipes - MEDIUM : logs: Only attempt to free startup_logs once. - MINOR : listener: keep accept rate counters accurate under saturation - MINOR : ssl: fix warning about ssl-min/max-ver support --- 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: 7 bug fixes in queue for next release
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.19 was issued on 2019/02/11. There are currently 7 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/03/11 - 3 MEDIUM, first one merged on 2019/03/11 - 2 MINOR, first one merged on 2019/03/11 Thus the computed ideal release date for 1.8.20 would be 2019/03/25, which was one week ago. The current list of patches in the queue is: - MAJOR : listener: Make sure the listener exist before using it. - MAJOR : spoe: Fix initialization of thread-dependent fields - MEDIUM : 51d: fix possible segfault on deinit_51degrees() - MEDIUM : threads/fd: do not forget to take into account epoll_fd/pipes - MEDIUM : logs: Only attempt to free startup_logs once. - MINOR : ssl: fix warning about ssl-min/max-ver support - MINOR : listener: keep accept rate counters accurate under saturation --- 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: 3 bug fixes in queue for next release
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.6 was issued on 2019/03/29. There are currently 3 patches in the queue cut down this way: - 1 MEDIUM, first one merged on 2019/04/03 - 2 MINOR, first one merged on 2019/04/03 Thus the computed ideal release date for 1.9.7 would be 2019/05/01, which is in four weeks or less. The current list of patches in the queue is: - MEDIUM : peers: fix a case where peer session is not cleanly reset on release. - MINOR : htx: Preserve empty HTX messages with an unprocessed parsing error - MINOR : cli: correctly handle abns in 'show cli sockets' --- 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: 7 bug fixes in queue for next release
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.19 was issued on 2019/02/11. There are currently 7 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/03/11 - 3 MEDIUM, first one merged on 2019/03/11 - 2 MINOR, first one merged on 2019/03/11 Thus the computed ideal release date for 1.8.20 would be 2019/03/25, which was two weeks ago. The current list of patches in the queue is: - MAJOR : spoe: Fix initialization of thread-dependent fields - MAJOR : listener: Make sure the listener exist before using it. - MEDIUM : logs: Only attempt to free startup_logs once. - MEDIUM : 51d: fix possible segfault on deinit_51degrees() - MEDIUM : threads/fd: do not forget to take into account epoll_fd/pipes - MINOR : listener: keep accept rate counters accurate under saturation - MINOR : ssl: fix warning about ssl-min/max-ver support --- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
stable-bot: NOTICE: 5 bug fixes in queue for next release
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.6 was issued on 2019/03/29. There are currently 5 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2019/04/03 - 2 MINOR, first one merged on 2019/04/03 Thus the computed ideal release date for 1.9.7 would be 2019/05/01, which is in three weeks or less. The current list of patches in the queue is: - MEDIUM : h2: Don't attempt to recv from h2_process_demux if we subscribed. - MEDIUM : peers: fix a case where peer session is not cleanly reset on release. - MEDIUM : htx: fix random premature abort of data transfers - MINOR : htx: Preserve empty HTX messages with an unprocessed parsing error - MINOR : cli: correctly handle abns in 'show cli sockets' --- 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: 7 bug fixes in queue for next release
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.19 was issued on 2019/02/11. There are currently 7 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/03/11 - 3 MEDIUM, first one merged on 2019/03/11 - 2 MINOR, first one merged on 2019/03/11 Thus the computed ideal release date for 1.8.20 would be 2019/03/25, which was three weeks ago. The current list of patches in the queue is: - MAJOR : spoe: Fix initialization of thread-dependent fields - MAJOR : listener: Make sure the listener exist before using it. - MEDIUM : threads/fd: do not forget to take into account epoll_fd/pipes - MEDIUM : 51d: fix possible segfault on deinit_51degrees() - MEDIUM : logs: Only attempt to free startup_logs once. - MINOR : listener: keep accept rate counters accurate under saturation - MINOR : ssl: fix warning about ssl-min/max-ver support --- 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: 7 bug fixes in queue for next release
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.19 was issued on 2019/02/11. There are currently 7 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/03/11 - 3 MEDIUM, first one merged on 2019/03/11 - 2 MINOR, first one merged on 2019/03/11 Thus the computed ideal release date for 1.8.20 would be 2019/03/25, which was four weeks ago. The current list of patches in the queue is: - MAJOR : listener: Make sure the listener exist before using it. - MAJOR : spoe: Fix initialization of thread-dependent fields - MEDIUM : threads/fd: do not forget to take into account epoll_fd/pipes - MEDIUM : 51d: fix possible segfault on deinit_51degrees() - MEDIUM : logs: Only attempt to free startup_logs once. - MINOR : listener: keep accept rate counters accurate under saturation - MINOR : ssl: fix warning about ssl-min/max-ver support --- 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: 55 bug fixes in queue for next release
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.6 was issued on 2019/03/29. There are currently 55 patches in
the queue cut down this way:
- 3 MAJOR, first one merged on 2019/04/16
- 36 MEDIUM, first one merged on 2019/04/03
- 16 MINOR, first one merged on 2019/04/03
Thus the computed ideal release date for 1.9.7 would be 2019/04/30, which is in
two weeks or less.
The current list of patches in the queue is:
- MAJOR : task: make sure never to delete a queued task
- MAJOR : http_fetch: Get the channel depending on the keyword used
- MAJOR : lb/threads: fix insufficient locking on round-robin LB
- MEDIUM : tasks: Make sure we modify global_tasks_mask with the rq_lock.
- MEDIUM : maps: only try to parse the default value when it's present
- MEDIUM : htx: Don't return the start-line if the HTX message is empty
- MEDIUM : stream: Don't clear the stream_interface flags in
si_update_both.
- MEDIUM : listener: use a self-locked list for the dequeue lists
- MEDIUM : stream: Don't request a server connection if a shutw was
scheduled
- MEDIUM : list: fix LIST_POP_LOCKED's removal of the last pointer
- MEDIUM : streams: Store prev_state before calling si_update_both().
- MEDIUM : thread/http: Add missing locks in set-map and add-acl HTTP rules
- MEDIUM : list: add missing store barriers when updating elements and head
- MEDIUM : list: fix again LIST_ADDQ_LOCKED
- MEDIUM : htx: Defrag if blocks position is changed and the payloads wrap
- MEDIUM : streams: Don't remove the SI_FL_ERR flag in si_update_both().
- MEDIUM : mux-h1: Enable TCP splicing to exchange data only
- MEDIUM : tasks: Make sure we set TASK_QUEUED before adding a task to the
rq.
- MEDIUM : map: Fix memory leak in the map converter
- MEDIUM : peers: fix a case where peer session is not cleanly reset on
release.
- MEDIUM : h2: Don't attempt to recv from h2_process_demux if we
subscribed.
- MEDIUM : pattern: assign pattern IDs after checking the config validity
- MEDIUM : task/threads: address a fairness issue between local and global
tasks
- MEDIUM : streams: Only re-run process_stream if we're in a connected
state.
- MEDIUM : h1: Don't parse chunks CRLF if not enough data are available
- MEDIUM : list: correct fix for LIST_POP_LOCKED's removal of last element
- MEDIUM : h2: Make sure we're not already in the send_list in
h2_subscribe().
- MEDIUM : list: fix the rollback on addq in the locked liss
- MEDIUM : htx: Fix the process of HTTP CONNECT with h2 connections
- MEDIUM : mux-h1: Notify the stream waiting for TCP splicing if ibuf is
empty
- MEDIUM : applets: Don't use task_in_rq().
- MEDIUM : spoe: Queue message only if no SPOE applet is attached to the
stream
- MEDIUM : spoe: Return an error if nothing is encoded for fragmented
messages
- MEDIUM : list: fix incorrect pointer unlocking in LIST_DEL_LOCKED()
- MEDIUM : stream_interface: Don't bother doing chk_rcv/snd if not
connected.
- MEDIUM : htx: fix random premature abort of data transfers
- MEDIUM : listener: make sure the listener never accepts too many conns
- MEDIUM : htx: Don't crush blocks payload when append is done on a data
block
- MEDIUM : lists: Properly handle the case we're removing the first elt.
- MINOR : spoe: Be sure to set tv_request when each message fragment is
encoded
- MINOR : mworker: ensure that we still quits with SIGINT
- MINOR : ssl: Fix 48 byte TLS ticket key rotation
- MINOR : tasks: make sure the first task to be queued keeps its nice
value
- MINOR : htx: Preserve empty HTX messages with an unprocessed parsing
error
- MINOR : da: Get the request channel to call CHECK_HTTP_MESSAGE_FIRST()
- MINOR : acl: properly detect pattern type SMP_T_ADDR
- MINOR : mworker: disable busy polling in the master process
- MINOR : mux-h1: Don't switch the parser in busy mode if other side has
done
- MINOR : http_fetch/htx: Allow permissive sample prefetch for the HTX
- MINOR : mux-h1: Process input even if the input buffer is empty
- MINOR : mworker: don't exit with an ambiguous value
- MINOR : 51d: Get the request channel to call CHECK_HTTP_MESSAGE_FIRST()
- MINOR : threads: fix the process range of thread masks
- MINOR : mux-h1: Handle the flag CS_FL_KILL_CONN during a shutdown
read/write
- MINOR : cli: correctly handle abns in 'show cli sockets'
---
The hap
stable-bot: WARNING: 33 bug fixes in queue for next release
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.19 was issued on 2019/02/11. There are currently 33 patches in the queue cut down this way: - 5 MAJOR, first one merged on 2019/03/11 - 19 MEDIUM, first one merged on 2019/03/11 - 9 MINOR, first one merged on 2019/03/11 Thus the computed ideal release date for 1.8.20 would be 2019/03/25, which was five weeks ago. The current list of patches in the queue is: - MAJOR : listener: Make sure the listener exist before using it. - MAJOR : spoe: Fix initialization of thread-dependent fields - MAJOR : http_fetch: Get the channel depending on the keyword used - MAJOR : stats: Fix how huge POST data are read from the channel - MAJOR : checks: segfault during tcpcheck_main - MEDIUM : listener: use a self-locked list for the dequeue lists - MEDIUM : listener: make sure the listener never accepts too many conns - MEDIUM : list: fix the rollback on addq in the locked liss - MEDIUM : logs: Only attempt to free startup_logs once. - MEDIUM : pattern: assign pattern IDs after checking the config validity - MEDIUM : ssl: ability to set TLS 1.3 ciphers using ssl-default-server-ciphersuites - MEDIUM : list: fix LIST_POP_LOCKED's removal of the last pointer - MEDIUM : list: add missing store barriers when updating elements and head - MEDIUM : lists: Properly handle the case we're removing the first elt. - MEDIUM : maps: only try to parse the default value when it's present - MEDIUM : peers: fix a case where peer session is not cleanly reset on release. - MEDIUM : 51d: fix possible segfault on deinit_51degrees() - MEDIUM : thread/http: Add missing locks in set-map and add-acl HTTP rules - MEDIUM : list: fix incorrect pointer unlocking in LIST_DEL_LOCKED() - MEDIUM : list: fix again LIST_ADDQ_LOCKED - MEDIUM : list: correct fix for LIST_POP_LOCKED's removal of last element - MEDIUM : spoe: Return an error if nothing is encoded for fragmented messages - MEDIUM : spoe: Queue message only if no SPOE applet is attached to the stream - MEDIUM : threads/fd: do not forget to take into account epoll_fd/pipes - MINOR : acl: properly detect pattern type SMP_T_ADDR - MINOR : spoe: Don't systematically wakeup SPOE stream in the applet handler - MINOR : da: Get the request channel to call CHECK_HTTP_MESSAGE_FIRST() - MINOR : 51d: Get the request channel to call CHECK_HTTP_MESSAGE_FIRST() - MINOR : cli: correctly handle abns in 'show cli sockets' - MINOR : http/counters: fix missing increment of fe->srv_aborts - MINOR : ssl: fix warning about ssl-min/max-ver support - MINOR : listener: keep accept rate counters accurate under saturation - MINOR : threads: fix the process range of thread masks --- 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: 6 bug fixes in queue for next release
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.20 was issued on 2019/04/25. There are currently 6 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/04/30 - 4 MEDIUM, first one merged on 2019/04/29 - 1 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which is in two weeks or less. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request --- 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
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.7 was issued on 2019/04/25. There are currently 14 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/04/30 - 9 MEDIUM, first one merged on 2019/04/29 - 4 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.9.8 would be 2019/05/14, which is in two weeks or less. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MEDIUM : channels: Don't forget to reset output in channel_erase(). - MEDIUM : pattern: fix memory leak in regex pattern functions - MEDIUM : servers: fix typo "src" instead of "srv" - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : mux-h2: properly deal with too large headers frames - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : connections: Make sure we remove CO_FL_SESS_IDLE on disown. - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MINOR : haproxy: fix rule->file memory leak - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request - MINOR : checks: free memory allocated for tasklets - MINOR : log: properly free memory on logformat parse error and 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: WARNING: 34 bug fixes in queue for next release
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.7 was issued on 2019/04/25. There are currently 34 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/04/30 - 21 MEDIUM, first one merged on 2019/04/29 - 12 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.9.8 would be 2019/05/14, which is in one week or less. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MEDIUM : checks: make sure the warmup task takes the server lock - MEDIUM : h2: Make sure we set send_list to NULL in h2_detach(). - MEDIUM : mux-h2: properly deal with too large headers frames - MEDIUM : h2: Revamp the way send subscriptions works. - MEDIUM : streams: Don't add CF_WRITE_ERROR if early data were rejected. - MEDIUM : h2/htx: never leave a trailers block alone with no EOM block - MEDIUM : connections: Make sure we remove CO_FL_SESS_IDLE on disown. - MEDIUM : ssl: Use the early_data API the right way. - MEDIUM : h2: Don't check send_wait to know if we're in the send_list. - MEDIUM : channels: Don't forget to reset output in channel_erase(). - MEDIUM : servers: fix typo "src" instead of "srv" - MEDIUM : http: Use pointer to the begining of input to parse message headers - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : ssl: Don't attempt to use early data with libressl. - MEDIUM : pattern: fix memory leak in regex pattern functions - MEDIUM : spoe: Be sure the sample is found before setting its context - MEDIUM : h2/htx: always fail on too large trailers - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : mux-h2/htx: never wait for EOM when processing trailers - MINOR : logs/threads: properly split the log area upon startup - MINOR : mux-h1: Fix the parsing of trailers - MINOR : mux-h2: fix the condition to close a cs-less h2s on the backend - MINOR : mworker/ssl: close OpenSSL FDs on reload - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request - MINOR : log: properly free memory on logformat parse error and deinit() - MINOR : mux-h2: rely on trailers output not input to turn them to empty data - MINOR : stream: Attach the read side on the response as soon as possible - MINOR : checks: free memory allocated for tasklets - MINOR : htx: Never transfer more than expected in htx_xfer_blks() - MINOR : haproxy: fix rule->file memory leak - MINOR : activity: always initialize the profiling variable --- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
stable-bot: WARNING: 6 bug fixes in queue for next release
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.20 was issued on 2019/04/25. There are currently 6 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/04/30 - 4 MEDIUM, first one merged on 2019/04/29 - 1 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which is in one week or less. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : port_range: Make the ring buffer lock-free. - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request --- 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: 1 bug fixes in queue for next release
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.8 was issued on 2019/05/13. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2019/05/16 Thus the computed ideal release date for 1.9.9 would be 2019/06/13, which is in four weeks or less. The current list of patches in the queue is: - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" --- 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: 7 bug fixes in queue for next release
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.20 was issued on 2019/04/25. There are currently 7 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/04/30 - 4 MEDIUM, first one merged on 2019/04/29 - 2 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which was within the last week. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" --- 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: 10 bug fixes in queue for next release
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.8 was issued on 2019/05/13. There are currently 10 patches in the queue cut down this way: - 6 MEDIUM, first one merged on 2019/05/21 - 4 MINOR, first one merged on 2019/05/16 Thus the computed ideal release date for 1.9.9 would be 2019/06/13, which is in three weeks or less. The current list of patches in the queue is: - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : proto-htx: Not forward too much data when 1xx reponses are handled - MEDIUM : WURFL: segfault in wurfl-get() with missing info. - MEDIUM : dns: make the port numbers unsigned - MEDIUM : threads: Fix build for 32bits arch with dwcas. - MEDIUM : streams: Don't switch from SI_ST_CON to SI_ST_DIS on read0. - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : htx: Remove a forgotten while loop in htx_defrag() - MINOR : mux-h2: Count EOM in bytes sent when a HEADERS frame is formatted - MINOR : mux-h1: Report EOI instead EOS on parsing error or H2 upgrade --- 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: 9 bug fixes in queue for next release
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.20 was issued on 2019/04/25. There are currently 9 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/04/30 - 6 MEDIUM, first one merged on 2019/04/29 - 2 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which was one week ago. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : dns: make the port numbers unsigned - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request --- 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: 14 bug fixes in queue for next release
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.8 was issued on 2019/05/13. There are currently 14 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/05/27 - 8 MEDIUM, first one merged on 2019/05/21 - 5 MINOR, first one merged on 2019/05/16 Thus the computed ideal release date for 1.9.9 would be 2019/06/10, which is in one week or less. The current list of patches in the queue is: - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : threads: Fix build for 32bits arch with dwcas. - MEDIUM : dns: make the port numbers unsigned - MEDIUM : proto-htx: Not forward too much data when 1xx reponses are handled - MEDIUM : streams: Don't switch from SI_ST_CON to SI_ST_DIS on read0. - MEDIUM : queue: fix the tree walk in pendconn_redistribute. - MEDIUM : WURFL: segfault in wurfl-get() with missing info. - MEDIUM : threads: fix double-word CAS on non-optimized 32-bit platforms - MINOR : ssl_sock: Fix memory leak when disabling compression - MINOR : mux-h2: Count EOM in bytes sent when a HEADERS frame is formatted - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : mux-h1: Report EOI instead EOS on parsing error or H2 upgrade - MINOR : htx: Remove a forgotten while loop in htx_defrag() --- 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: 11 bug fixes in queue for next release
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.20 was issued on 2019/04/25. There are currently 11 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/04/30 - 6 MEDIUM, first one merged on 2019/04/29 - 3 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which was two weeks ago. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : dns: make the port numbers unsigned - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request - MINOR : ssl_sock: Fix memory leak when disabling compression --- 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: 11 bug fixes in queue for next release
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.20 was issued on 2019/04/25. There are currently 11 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/04/30 - 6 MEDIUM, first one merged on 2019/04/29 - 3 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which was three weeks ago. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : dns: make the port numbers unsigned - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request - MINOR : ssl_sock: Fix memory leak when disabling compression --- 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: 30 bug fixes in queue for next release
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.8 was issued on 2019/05/13. There are currently 30 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/05/27 - 17 MEDIUM, first one merged on 2019/05/21 - 12 MINOR, first one merged on 2019/05/16 Thus the computed ideal release date for 1.9.9 would be 2019/06/10, which was within the last week. The current list of patches in the queue is: - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : connection: Use the session to get the origin address if needed. - MEDIUM : mux-h1: Don't skip the TCP splicing when there is no more data to read - MEDIUM : queue: fix the tree walk in pendconn_redistribute. - MEDIUM : mux-h1: only check input data for the current stream, not next one - MEDIUM : streams: Don't switch from SI_ST_CON to SI_ST_DIS on read0. - MEDIUM : h2: Don't forget to set h2s->cs to NULL after having free'd cs. - MEDIUM : threads: Fix build for 32bits arch with dwcas. - MEDIUM : threads: fix double-word CAS on non-optimized 32-bit platforms - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : WURFL: segfault in wurfl-get() with missing info. - MEDIUM : vars: make the tcp/http unset-var() action support conditions - MEDIUM : vars: make sure the scope is always valid when accessing vars - MEDIUM : connection: fix multiple handshake polling issues - MEDIUM : http: fix "http-request reject" when not final - MEDIUM : mux-h1: Don't switch the mux in BUSY mode on 1xx messages - MEDIUM : dns: make the port numbers unsigned - MEDIUM : proto-htx: Not forward too much data when 1xx reponses are handled - MINOR : mux-h2: Count EOM in bytes sent when a HEADERS frame is formatted - MINOR : mux-h1: Wake up the mux if it is busy when a 1xx response is handled - MINOR : peers: Wrong stick-table update message building. - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : deinit/threads: make hard-stop-after perform a clean exit - MINOR : mux-h1: Don't send more data than expected - MINOR : htx: Remove a forgotten while loop in htx_defrag() - MINOR : mux-h1: errflag must be set on H1S and not H1M during output processing - MINOR : mux-h1: Report EOI instead EOS on parsing error or H2 upgrade - MINOR : time: make sure only one thread sets global_now at boot - MINOR : ssl_sock: Fix memory leak when disabling compression - MINOR : channel/htx: Don't alter channel during forward for empty 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: WARNING: 30 bug fixes in queue for next release
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.8 was issued on 2019/05/13. There are currently 30 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/05/27 - 17 MEDIUM, first one merged on 2019/05/21 - 12 MINOR, first one merged on 2019/05/16 Thus the computed ideal release date for 1.9.9 would be 2019/06/10, which was one week ago. The current list of patches in the queue is: - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : connection: Use the session to get the origin address if needed. - MEDIUM : vars: make the tcp/http unset-var() action support conditions - MEDIUM : mux-h1: only check input data for the current stream, not next one - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : connection: fix multiple handshake polling issues - MEDIUM : vars: make sure the scope is always valid when accessing vars - MEDIUM : h2: Don't forget to set h2s->cs to NULL after having free'd cs. - MEDIUM : threads: Fix build for 32bits arch with dwcas. - MEDIUM : threads: fix double-word CAS on non-optimized 32-bit platforms - MEDIUM : queue: fix the tree walk in pendconn_redistribute. - MEDIUM : mux-h1: Don't switch the mux in BUSY mode on 1xx messages - MEDIUM : dns: make the port numbers unsigned - MEDIUM : http: fix "http-request reject" when not final - MEDIUM : mux-h1: Don't skip the TCP splicing when there is no more data to read - MEDIUM : proto-htx: Not forward too much data when 1xx reponses are handled - MEDIUM : WURFL: segfault in wurfl-get() with missing info. - MEDIUM : streams: Don't switch from SI_ST_CON to SI_ST_DIS on read0. - MINOR : channel/htx: Don't alter channel during forward for empty HTX message - MINOR : peers: Wrong stick-table update message building. - MINOR : mux-h2: Count EOM in bytes sent when a HEADERS frame is formatted - MINOR : deinit/threads: make hard-stop-after perform a clean exit - MINOR : mux-h1: Don't send more data than expected - MINOR : mux-h1: errflag must be set on H1S and not H1M during output processing - MINOR : mux-h1: Wake up the mux if it is busy when a 1xx response is handled - MINOR : time: make sure only one thread sets global_now at boot - MINOR : ssl_sock: Fix memory leak when disabling compression - MINOR : htx: Remove a forgotten while loop in htx_defrag() - MINOR : mux-h1: Report EOI instead EOS on parsing error or H2 upgrade - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" --- 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: 11 bug fixes in queue for next release
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.20 was issued on 2019/04/25. There are currently 11 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/04/30 - 6 MEDIUM, first one merged on 2019/04/29 - 3 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which was four weeks ago. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : dns: make the port numbers unsigned - MINOR : ssl_sock: Fix memory leak when disabling compression - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request --- 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: 50 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.8 was issued on 2019/05/13. There are currently 50 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/05/27 - 28 MEDIUM, first one merged on 2019/05/21 - 21 MINOR, first one merged on 2019/05/16 Thus the computed ideal release date for 1.9.9 would be 2019/06/10, which was two weeks ago. The current list of patches in the queue is: - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : mux-h1: only check input data for the current stream, not next one - MEDIUM : h2: Don't forget to set h2s->cs to NULL after having free'd cs. - MEDIUM : queue: fix the tree walk in pendconn_redistribute. - MEDIUM : streams: Don't switch from SI_ST_CON to SI_ST_DIS on read0. - MEDIUM : mux-h1: Don't skip the TCP splicing when there is no more data to read - MEDIUM : proto_htx: Introduce the state ENDING during forwarding - MEDIUM : h2/htx: Update data length of the HTX when the cookie list is built - MEDIUM : proto-htx: Not forward too much data when 1xx reponses are handled - MEDIUM : vars: make the tcp/http unset-var() action support conditions - MEDIUM : WURFL: segfault in wurfl-get() with missing info. - MEDIUM : connection: Use the session to get the origin address if needed. - MEDIUM : mux-h2: Reset padlen when several frames are demux - MEDIUM : lb_fwlc: Don't test the server's lb_tree from outside the lock - MEDIUM : connections: Don't call shutdown() if we want to disable linger. - MEDIUM : connection: fix multiple handshake polling issues - MEDIUM : threads: fix double-word CAS on non-optimized 32-bit platforms - MEDIUM : http: fix "http-request reject" when not final - MEDIUM : dns: make the port numbers unsigned - MEDIUM : mux-h1: Don't switch the mux in BUSY mode on 1xx messages - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : compression/htx: Fix the adding of the last data block - MEDIUM : threads: Fix build for 32bits arch with dwcas. - MEDIUM : connections: Don't try to send early data if we have no mux. - MEDIUM : mux-h2: Remove the padding length when a DATA frame size is checked - MEDIUM : compression: Set Vary: Accept-Encoding for compressed responses - MEDIUM : mux-h2: make sure the connection timeout is always set - MEDIUM : connections: Don't use ALPN to pick mux when in mode TCP. - MEDIUM : vars: make sure the scope is always valid when accessing vars - MINOR : mux-h2: Count EOM in bytes sent when a HEADERS frame is formatted - MINOR : flt_trace/htx: Only apply the random forwarding on the message body. - MINOR : deinit/threads: make hard-stop-after perform a clean exit - MINOR : channel/htx: Don't alter channel during forward for empty HTX message - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : 51d/htx: The _51d_fetch method, and the methods it calls are now HTX aware. - MINOR : http-rules: mention "deny_status" for "deny" in the error message - MINOR : mux-h1: errflag must be set on H1S and not H1M during output processing - MINOR : peers: Wrong stick-table update message building. - MINOR : channel/htx: Call channel_htx_full() from channel_full() - MINOR : ssl_sock: Fix memory leak when disabling compression - MINOR : time: make sure only one thread sets global_now at boot - MINOR : lua/htx: Make txn.req_req_* and txn.res_rep_* HTX aware - MINOR : htx: Remove a forgotten while loop in htx_defrag() - MINOR : mux-h1: Report EOI instead EOS on parsing error or H2 upgrade - MINOR : fl_trace/htx: Be sure to always forward trailers and EOM - MINOR : mux-h1: Add the header connection in lower case in outgoing messages - MINOR : http: Use the global value to limit the number of parsed headers - MINOR : mux-h1: Wake up the mux if it is busy when a 1xx response is handled - MINOR : mux-h1: Wake busy mux for I/O when message is fully sent - MINOR : mux-h1: Don't send more data than expected --- 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: 20 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.20 was issued on 2019/04/25. There are currently 20 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/04/30 - 13 MEDIUM, first one merged on 2019/04/29 - 5 MINOR, first one merged on 2019/04/29 Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which was five weeks ago. The current list of patches in the queue is: - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MEDIUM : mux-h2: make sure the connection timeout is always set - MEDIUM : lb_fwlc: Don't test the server's lb_tree from outside the lock - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to strdup it - MEDIUM : dns: make the port numbers unsigned - MEDIUM : vars: make sure the scope is always valid when accessing vars - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : vars: make the tcp/http unset-var() action support conditions - MEDIUM : port_range: Make the ring buffer lock-free. - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : http: fix "http-request reject" when not final - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : compression: Set Vary: Accept-Encoding for compressed responses - MEDIUM : connection: fix multiple handshake polling issues - MINOR : ssl_sock: Fix memory leak when disabling compression - MINOR : http_fetch: Rely on the smp direction for "cookie()" and "hdr()" - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request - MINOR : deinit/threads: make hard-stop-after perform a clean exit - MINOR : http-rules: mention "deny_status" for "deny" in the 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: 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.0 was issued on 2019/06/16. There are currently 9 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2019/06/21 - 6 MEDIUM, first one merged on 2019/06/17 - 2 MINOR, first one merged on 2019/06/17 Thus the computed ideal release date for 2.0.1 would be 2019/07/05, which is in two weeks or less. The current list of patches in the queue is: - MAJOR : sample: Wrong stick-table name parsing in "if/unless" ACL condition. - MEDIUM : mux-h2: Remove the padding length when a DATA frame size is checked - MEDIUM : lb_fwlc: Don't test the server's lb_tree from outside the lock - MEDIUM : compression: Set Vary: Accept-Encoding for compressed responses - MEDIUM : mux-h2: Reset padlen when several frames are demux - MEDIUM : h2/htx: Update data length of the HTX when the cookie list is built - MEDIUM : htx: Fully update HTX message when the block value is changed - MINOR : mux-h1: Add the header connection in lower case in outgoing messages - MINOR : lua/htx: Make txn.req_req_* and txn.res_rep_* HTX aware --- 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.
