Stream ws_client has a bug related to the time library

[EyalPazz]

What happened (please include outputs or screenshots):
{OverflowError}OverflowError('timestamp too large to convert to C _PyTime_t')

What you expected to happen:
Not Crash

How to reproduce it (as minimally and precisely as possible):
run WSClient.readline_channel with default values

Anything else we need to know?:

the problem is here:
if timeout is None: timeout = float("inf")
I fixed it, just want to know if i should open a PR

Environment:

• Kubernetes version (kubectl version): v1.27.1
• OS (e.g., MacOS 10.13.6): Ubuntu 22.04
• Python version (python --version): Python 3.10.12
• Python client version (pip list | grep kubernetes): 30.1.0

[yliaog]

please open a PR

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten