nic-6443 opened a new pull request, #13697: URL: https://github.com/apache/apisix/pull/13697
### Description Bump apisix-runtime from 1.3.9 to 1.3.10, which picks up [apisix-nginx-module 1.19.8](https://github.com/api7/apisix-nginx-module/releases/tag/1.19.8). It fixes several long-standing defects in the runtime patches: - balancer keepalive pools are now keyed by the full pool name instead of a crc32 digest (colliding pool names could silently share connections across unrelated upstream pools), the default pool identity covers connect-time properties (local bind address, TLS server name), and `set_current_peer(addr, port, host)` accepts the documented host argument again; - `ngx.socket.stream():sslhandshake()` no longer fails with an undefined FFI symbol, and `tlshandshake()` no longer mutates the caller's options table (reusing the same file-based mTLS options across connections works now); - xRPC `move()`/`reset_read_buf()` reject a source socket with a pending read instead of corrupting the in-flight data, and the reset recycles the whole receive chain instead of leaking middle nodes into the request pool; - privileged agent listeners (`enable_process=privileged_agent`, used by the status API server) are now opened and owned by the master process: a bind conflict fails startup loudly instead of leaving a healthy-looking nginx without the listener, reloads no longer have a no-listener window, socket options on those listeners actually take effect, and the address-conflict error reports the actual owner role. The runtime-debug checksums in `ci/linux-install-openresty.sh` are updated from the published release artifacts. ### Checklist - [x] I have explained the need for this PR and the problem it solves - [x] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [x] I have updated the documentation to reflect this change - [x] I have verified that this change is backward compatible -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
