-
Notifications
You must be signed in to change notification settings - Fork 182
watch stream: don't unmarshal responses when streaming log #185
watch stream: don't unmarshal responses when streaming log #185
Conversation
@roycaihw: GitHub didn't allow me to request PR reviews from the following users: Ark-kun. Note that only kubernetes-client members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: roycaihw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #185 +/- ##
==========================================
+ Coverage 92.46% 92.52% +0.05%
==========================================
Files 13 13
Lines 1487 1485 -2
==========================================
- Hits 1375 1374 -1
+ Misses 112 111 -1
Continue to review full report at Codecov.
|
adding a test in main repo: kubernetes-client/python#1087 |
/hold cancel This change is ready for review. Please take a look |
Thank you for walking me through the changes and the background personally. :) /lgtm |
CHANGELOG --- - Logs are no longer unmarshalled when streaming [kubernetes-client/python-base#185](https://github.com/kubernetes-client/python-base/pulls/185)
We were doing a best-effort unmarshalling for both pod log and regular watches, but we really shouldn't try unmarshalling pod logs into watch events. The existing code would unmarshal a pod log that happens to be a JSON blob and contains a field "object".
/hold
We need an e2e test for basic watch functionality in the main repo first.
/cc @Ark-kun @palnabarun