Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Configure default timeout for all API calls

未關閉
#1,961 31 則留言 8 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@yliaog 已經在處理了。

開始於 2022年12月5日。

評估

這個 Issue 還沒有評估資料。

描述

kind/feature lifecycle/rotten

What is the feature and why do you need it:
All API calls done through this client today goes through urllib3, where the timeout is default to set to None, this means infinite timeout and is a well known pitfall with urllib3. Lost connection attempts can get stuck waiting forever, with no retries being done to reestablish the connection.

Quoting the requests-documentation which uses urllib3 under the hood:

Nearly all production code should use this parameter in nearly all requests. Failure to do so can cause your program to hang indefinitely:


There is a _request_timeout kwargs argument that can be set on each api-call, but that is both tedious, easy to forget and not type-checked due to use of kwargs-dictionarly.

Describe the solution you'd like to see:
Similar to how retries is configured, Configuration should accept a timeout-argument, this can be forwarded into urllib3s poolmanager where it uses this timeout for all operations where an explicit timeout is not provided.

主要語言
Python
星號
7.7k
分支
3.5k
平均合併
1 天 13 小時
30 天內合併 PR
21

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

kubernetes-client/python 的其他 Issue

查看 kubernetes-client/python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。