hachi029 opened a new pull request, #12779:
URL: https://github.com/apache/apisix/pull/12779
### Description
when there is any timeout sub request, the number of sub responses does not
match the number of sub requests。
for example:
the batch-request with 2 sub requests
`{"headers":{},"pipeline":[{"path":"/quick","method":"GET"},{"path":"/slow","method":"GET"}]}`
there are 3 sub responses in the batch-response, with an extra empty json
empty '{}'
`[{"status":200,"body":"quick","reason":"OK","headers":{"Connection":"keep-alive"}},{"status":504,"reason":"upstream
timeout"},{}]`
### Checklist
- [ ] I have explained the need for this PR and the problem it solves
- [ ] I have explained the changes or the new features added to this PR
- [ ] I have added tests corresponding to this change
- [ ] I have updated the documentation to reflect this change
- [ ] I have verified that this change is backward compatible (If not,
please discuss on the [APISIX mailing
list](https://github.com/apache/apisix/tree/master#community) first)
<!--
Note
1. Mark the PR as draft until it's ready to be reviewed.
2. Always add/update tests for any changes unless you have a good reason.
3. Always update the documentation to reflect the changes made in the PR.
4. Make a new commit to resolve conversations instead of `push -f`.
5. To resolve merge conflicts, merge master instead of rebasing.
6. Use "request review" to notify the reviewer after making changes.
7. Only a reviewer can mark a conversation as resolved.
-->
--
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]
