-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Add a E2E test for ws client sending binary payloads #1080
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Currently we only have text test cases. A binary payload test case can be copy a file to a pod and read it back. The request sent by this client will be similar to what Once we have the test, it would be great if we can also show the test fails if we exclude the fix kubernetes-client/python-base#152. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. 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. |
Ref kubernetes-client/python-base#152. We should have a test case for ws client sending bytes data in our e2e tests.
cc @sergei-maertens
The text was updated successfully, but these errors were encountered: