stable-bot: WARNING: 29 bug fixes in queue for next release - 1.8
Hi, This is a friendly bot that watches fixes pending for the next haproxy-stable release! One such e-mail is sent periodically once patches are waiting in the last maintenance branch, and an ideal release date is computed based on the severity of these fixes and their merge date. Responses to this mail must be sent to the mailing list. Last release 1.8.23 was issued on 2019/11/25. There are currently 29 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 8 MEDIUM, first one merged on 2019/12/05 - 19 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was five weeks ago. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MAJOR : dns: add minimalist error processing on the Rx path - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : sample: always check converters' arguments - MINOR : dns: allow srv record weight set to 0 - MINOR : listener: also clear the error flag on a paused listener - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : listener: do not immediately resume on transient error - MINOR : server: make "agent-addr" work on default-server line - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : stream: don't mistake match rules for store-request rules - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : listener: fix off-by-one in state name check - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : http_act: don't check capture id in backend - MINOR : log: fix minor resource leaks on logformat error path - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 --- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
stable-bot: WARNING: 29 bug fixes in queue for next release - 1.8
Hi, This is a friendly bot that watches fixes pending for the next haproxy-stable release! One such e-mail is sent periodically once patches are waiting in the last maintenance branch, and an ideal release date is computed based on the severity of these fixes and their merge date. Responses to this mail must be sent to the mailing list. Last release 1.8.23 was issued on 2019/11/25. There are currently 29 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2019/12/10 - 8 MEDIUM, first one merged on 2019/12/05 - 19 MINOR, first one merged on 2019/12/05 Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was four weeks ago. The current list of patches in the queue is: - MAJOR : dns: add minimalist error processing on the Rx path - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : listener/thread: fix a race when pausing a listener - MEDIUM : kqueue: Make sure we report read events even when no data. - MEDIUM : ssl: Don't set the max early data we can receive too early. - MEDIUM : listener/threads: fix a remaining race in the listener's accept() - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : proto_udp/threads: recv() and send() must not be exclusive. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mworker: remain in mworker mode during reload - MINOR : sample: always check converters' arguments - MINOR : listener: do not immediately resume on transient error - MINOR : listener: also clear the error flag on a paused listener - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : mworker: properly pass SIGTTOU/SIGTTIN to workers - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : listener/threads: always use atomic ops to clear the FD events - MINOR : ssl: certificate choice can be unexpected with openssl >= 1.1.1 - MINOR : sample: fix the closing bracket and LF in the debug converter - MINOR : log: fix minor resource leaks on logformat error path - MINOR : http_act: don't check capture id in backend - MINOR : proxy: make soft_stop() also close FDs in LI_PAUSED state - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : stream: don't mistake match rules for store-request rules - MINOR : listener: fix off-by-one in state name check - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : server: make "agent-addr" work on default-server line - MINOR : dns: allow srv record weight set to 0 --- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
stable-bot: WARNING: 29 bug fixes in queue for next release - 1.8
Hi, This is a friendly bot that watches fixes pending for the next haproxy-stable release! One such e-mail is sent periodically once patches are waiting in the last maintenance branch, and an ideal release date is computed based on the severity of these fixes and their merge date. Responses to this mail must be sent to the mailing list. Last release 1.8.20 was issued on 2019/04/25. There are currently 29 patches in the queue cut down this way: - 3 MAJOR, first one merged on 2019/04/30 - 20 MEDIUM, first one merged on 2019/04/29 - 6 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 ten weeks ago. The current list of patches in the queue is: - MAJOR : map/acl: real fix segfault during show map/acl on CLI - MAJOR : listener: fix thread safety in resume_listener() - MAJOR : lb/threads: make sure the avoided server is not full on second pass - MEDIUM : tcp-check: unbreak multiple connect rules again - MEDIUM : tcp-checks: do not dereference inexisting conn_stream - 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 : protocols: add a global lock for the init/deinit stuff - MEDIUM : da: cast the chunk to string. - MEDIUM : connection: fix multiple handshake polling issues - MEDIUM : spoe: arg len encoded in previous frag frame but len changed - MEDIUM : mux-h2: make sure the connection timeout is always set - MEDIUM : dns: make the port numbers unsigned - MEDIUM : compression: Set Vary: Accept-Encoding for compressed responses - MEDIUM : lb_fas: Don't test the server's lb_tree from outside the lock - MEDIUM : lb-chash: Fix the realloc() when the number of nodes is increased - MEDIUM : http/htx: unbreak option http_proxy - MEDIUM : vars: make the tcp/http unset-var() action support conditions - MEDIUM : vars: make sure the scope is always valid when accessing vars - MEDIUM : http: fix "http-request reject" when not final - MEDIUM : spoe: Don't use the SPOE applet after releasing it - MEDIUM : listener: Fix how unlimited number of consecutive accepts is handled - MEDIUM : port_range: Make the ring buffer lock-free. - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per request - MINOR : http-rules: mention "deny_status" for "deny" in the error message - MINOR : deinit/threads: make hard-stop-after perform a clean exit - MINOR : ssl_sock: Fix memory leak when disabling compression - MINOR : proxy: always lock stop_proxy() - 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: 29 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 every week 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.9 was issued on 2018/05/18. There are currently 29 patches in
the queue cut down this way:
- 2 BUILD, first one merged on 2018/05/23
- 2 MAJOR, first one merged on 2018/06/06
- 15 MEDIUM, first one merged on 2018/05/23
- 10 MINOR, first one merged on 2018/05/23
Thus the computed ideal release date for 1.8.10 would be 2018/06/20, which was
within the last week.
The current list of patches in the queue is:
- BUILD : threads: unbreak build without threads
- BUILD : fd: fix typo causing a warning when threads are disabled
- MAJOR : map: fix a segfault when using http-request set-map
- MAJOR : lua: Dead lock with sockets
- MEDIUM : spoe: Return an error when the wrong ACK is received in sync
mode
- MEDIUM : lua/socket: Sheduling error on write: may dead-lock
- MEDIUM : cache: don't cache when an Authorization header is present
- MEDIUM : threads: handle signal queue only in thread 0
- MEDIUM : contrib/modsecurity: Use network order to encode/decode flags
- MEDIUM : contrib/mod_defender: Use network order to encode/decode flags
- MEDIUM : fd: Only check update_mask against all_threads_mask.
- MEDIUM : spoe: Flags are not encoded in network order
- MEDIUM : stick-tables: Decrement ref_cnt in table_* converters
- MEDIUM : lua/socket: wrong scheduling for sockets
- MEDIUM : dns: Delay the attempt to run a DNS resolution on check failure.
- MEDIUM : lua/socket: Length required read doesn't work
- MEDIUM : lua/socket: Notification error
- MEDIUM : lua/socket: Buffer error, may segfault
- MEDIUM : servers: Add srv_addr default placeholder to the state file
- MINOR : contrib/mod_defender: update pointer on the end of the frame
- MINOR : lua: Socket.send threw runtime error: 'close' needs 1 arguments.
- MINOR : unix: Make sure we can transfer abns sockets on seamless reload.
- MINOR : contrib/mod_defender: Don't reset the status code during
disconnect
- MINOR : don't ignore SIG{BUS,FPE,ILL,SEGV} during signal processing
- MINOR : contrib/modsecurity: Don't reset the status code during
disconnect
- MINOR : signals: ha_sigmask macro for multithreading
- MINOR : contrib/modsecurity: update pointer on the end of the frame
- MINOR : ssl/lua: prevent lua from affecting automatic maxconn
computation
- MINOR : contrib/spoa_example: Don't reset the status code during
disconnect
---
The haproxy stable-bot is freely provided by HAProxy Technologies to help
improve the quality of each HAProxy release. If you have any issue with these
emails or if you want to suggest some improvements, please post them on the
list so that the solutions suiting the most users can be found.
stable-bot: WARNING: 29 bug fixes in queue for next release
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent every week 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.9 was issued on 2018/05/18. There are currently 29 patches in
the queue cut down this way:
- 2 BUILD, first one merged on 2018/05/23
- 2 MAJOR, first one merged on 2018/06/06
- 15 MEDIUM, first one merged on 2018/05/23
- 10 MINOR, first one merged on 2018/05/23
Thus the computed ideal release date for 1.8.10 would be 2018/06/20, which is
in one week or less.
The current list of patches in the queue is:
- BUILD : fd: fix typo causing a warning when threads are disabled
- BUILD : threads: unbreak build without threads
- MAJOR : map: fix a segfault when using http-request set-map
- MAJOR : lua: Dead lock with sockets
- MEDIUM : contrib/mod_defender: Use network order to encode/decode flags
- MEDIUM : lua/socket: wrong scheduling for sockets
- MEDIUM : contrib/modsecurity: Use network order to encode/decode flags
- MEDIUM : lua/socket: Notification error
- MEDIUM : fd: Only check update_mask against all_threads_mask.
- MEDIUM : spoe: Return an error when the wrong ACK is received in sync
mode
- MEDIUM : threads: handle signal queue only in thread 0
- MEDIUM : lua/socket: Sheduling error on write: may dead-lock
- MEDIUM : servers: Add srv_addr default placeholder to the state file
- MEDIUM : dns: Delay the attempt to run a DNS resolution on check failure.
- MEDIUM : cache: don't cache when an Authorization header is present
- MEDIUM : spoe: Flags are not encoded in network order
- MEDIUM : stick-tables: Decrement ref_cnt in table_* converters
- MEDIUM : lua/socket: Buffer error, may segfault
- MEDIUM : lua/socket: Length required read doesn't work
- MINOR : contrib/modsecurity: Don't reset the status code during
disconnect
- MINOR : contrib/spoa_example: Don't reset the status code during
disconnect
- MINOR : don't ignore SIG{BUS,FPE,ILL,SEGV} during signal processing
- MINOR : contrib/modsecurity: update pointer on the end of the frame
- MINOR : unix: Make sure we can transfer abns sockets on seamless reload.
- MINOR : signals: ha_sigmask macro for multithreading
- MINOR : contrib/mod_defender: update pointer on the end of the frame
- MINOR : ssl/lua: prevent lua from affecting automatic maxconn
computation
- MINOR : contrib/mod_defender: Don't reset the status code during
disconnect
- MINOR : lua: Socket.send threw runtime error: 'close' needs 1 arguments.
---
The haproxy stable-bot is freely provided by HAProxy Technologies to help
improve the quality of each HAProxy release. If you have any issue with these
emails or if you want to suggest some improvements, please post them on the
list so that the solutions suiting the most users can be found.
