fix: correct ResponseRecorder hijack state tracking#16611
Conversation
Signed-off-by: immanuwell <pchpr.00@list.ru>
|
Welcome @immanuwell! It looks like this is your first PR to knative/serving 🎉 |
|
Hi @immanuwell. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
|
/lgtm thanks for the fix! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, immanuwell The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #16611 +/- ##
==========================================
+ Coverage 80.22% 80.28% +0.05%
==========================================
Files 217 217
Lines 13568 13568
==========================================
+ Hits 10885 10893 +8
+ Misses 2316 2310 -6
+ Partials 367 365 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Proposed Changes
ResponseRecorderRepro
go test ./pkg/http -run TestResponseRecorder -count=1failed_hijackends up with202instead of502successful_hijackthe wrong way, kinda backwardsRelease Note