From 10cae2e135e0e93e08c887ebbdb7a065c67839f3 Mon Sep 17 00:00:00 2001
From: HAProxy Community
- Converted with haproxy-dconv v0.4.2-15 on 2024/12/19 + Converted with haproxy-dconv v0.4.2-15 on 2024/12/20
@@ -4439,7 +4439,7 @@version 3.2-dev1-74
+version 3.2-dev1-75
2024/12/11
@@ -7185,6 +7185,7 @@
Explicitly tell haproxy how haproxy sample objects should be handled when +pushed to Lua. Indeed, when leveraging native converters, sample fetches or +variables from Lua script (to name a few), haproxy converts the internal +smp type to equivalent Lua type. Because of historical implementation, there +is an ambiguity around boolean handling: when doing Lua -> haproxy smp +conversion, booleans are properly preserved, but when doing haproxy +smp -> Lua conversion, booleans were converted to integers by mistake. This +means that a sample fetch or converter returning a boolean would return an +integer 0 or 1 when leveraged from Lua. Unfortunately, in Lua, booleans and +integers are not interchangeable. Thus, to avoid ambiguities, +"tune.lua.bool-sample-conversion" must explicitly be set to either "normal" +(which means dropping the historical behavior for better consistency) or +"pre-3.1-bug" (enforce historical behavior to prevent existing script logic +from misbehaving). If the option is not set explicitly and a Lua script is +loaded from the configuration, haproxy will emit a warning, and the option +will implicitly default to "pre-3.1-bug" to match with the historical +behavior. It is recommended to set this option to "normal" after ensuring +that in-use Lua scripts are properly handling bool haproxy samples as booleans.
The "burst" execution timeout applies to any Lua handler. If the handler fails to finish or yield before timeout is reached, it will be aborted to prevent thread contention, to prevent traffic from not being served for too @@ -9146,23 +9164,6 @@3.2.< dedicated to the tasks. By default, this timeout isn't set because a task may remain alive during of the lifetime of HAProxy. For example, a task used to check servers. -
Explicitly tell haproxy how haproxy sample objects should be handled when -pushed to Lua. Indeed, when using native converters or sample fetches from -Lua script, haproxy converts the smp type to equivalent Lua type. Because -of historical implementation, there is an ambiguity around boolean -handling: when doing Lua -> haproxy smp conversion, booleans are properly -preserved, but when doing haproxy smp -> Lua conversion, booleans were -converted to integers. This means that a sample fetch or converter returning -a boolean would return an integer 0 or 1 when leveraged from Lua. -Unfortunately, in Lua, booleans and integers are not interchangeable. Thus, -to avoid ambiguities, "tune.lua.smp-preserve-bool" must explicitly be set to -either "on" (which means dropping the historical behavior for better -consistency) or "off" (enforce historical behavior to prevent existing script -logic from misbehaving). If the option is not set explicitly and a Lua script -is loaded from the configuration, haproxy will emit a warning, and the option -will implicitly default to "off" to match with the historical behavior. When -possible, it is recommended to set this option to "on" after ensuring that -in-use Lua scripts are properly handling bool haproxy samples as booleans.
Sets the number of active checks per thread above which a thread will actively try to search a less loaded thread to run the health check, or queue it until the number of active checks running on it diminishes. The @@ -31758,7 +31759,7 @@11
- HAProxy 3.2-dev1-74 – Configuration Manual
+ HAProxy 3.2-dev1-75 – Configuration Manual
, 2024/12/11
- Converted with haproxy-dconv v0.4.2-15 on 2024/12/19 + Converted with haproxy-dconv v0.4.2-15 on 2024/12/20
@@ -495,7 +495,7 @@version 3.2-dev1-74
+version 3.2-dev1-75
@@ -2515,7 +2515,7 @@
- Converted with haproxy-dconv v0.4.2-15 on 2024/12/19 + Converted with haproxy-dconv v0.4.2-15 on 2024/12/20
@@ -665,7 +665,7 @@version 3.2-dev1-74
+version 3.2-dev1-75
@@ -5446,7 +5446,7 @@