moonming opened a new pull request, #14182:
URL: https://github.com/apache/apisix/pull/14182

   ### Description
   
   Bump two published LuaRocks dependencies:
   
   - `lua-resty-etcd`: `1.10.6-0` → `1.10.7-0`. Preserve collected watch events 
when the last response in a coalesced read is a progress notification. 
Upstream: https://github.com/api7/lua-resty-etcd/compare/v1.10.6...v1.10.7
   - `multipart`: `0.5.11-1` → `0.6.0-1`. Fix unquoted field names, quoted 
parameters, and multipart delimiter matching. Upstream: 
https://github.com/Kong/lua-multipart/compare/0.5.11-1...0.6.0-1
   
   Add HTTP regressions for unquoted multipart fields in `post_arg` route 
matching and for field names, quoted boundaries, and delimiter-like content in 
`body-transformer`. The existing mutation/re-encoding tests remain unchanged.
   
   ### Validation
   
   - `make deps` completed successfully with the updated manifest.
   - Nine complete Test::Nginx files passed, 346 assertions, using APISIX 
runtime `1.4.2` and a real etcd `3.5.15` instance:
   
     ```sh
     FLUSH_ETCD=1 ENABLE_LOCAL_DNS=1 prove --timer -Itest-nginx/lib -I. \
       t/plugin/body-transformer-multipart.t \
       t/core/etcd.t t/core/etcd-sync.t t/core/etcd-watch-start-revision.t \
       t/admin/routes_request_body.t t/core/ctx3.t t/core/request.t \
       t/plugin/body-transformer.t t/plugin/body-transformer2.t
     ```
   
   - Replacing only the installed `multipart.lua` with the official `0.5.11-1` 
implementation made exactly the new regressions fail: transformed field 
names/content were wrong, and the unquoted `post_arg.model` request returned 
404. All preexisting assertions in those two files still passed. After 
restoring `0.6.0-1`, both complete files passed again (46 assertions).
   - `luarocks lint`, `git diff --check`, and the repository's test reindex 
check passed.
   
   The upstream etcd fix depends on coalesced watch/progress responses. Its 
deterministic upstream regression uses a synthetic endpoint; the real-etcd 
integration suites here validate APISIX compatibility rather than 
deterministically reproduce that transport condition.
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes
   - [x] I have added regression tests corresponding to the multipart changes
   - [x] No configuration or API documentation changes are required
   - [x] I have verified compatibility with the targeted APISIX integration 
suites
   


-- 
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]

Reply via email to