microsoftgraph / microsoftgraph/msgraph-sdk-python
Excessive Informational Logs from Library During HTTP Requests
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 630
- 分支
- 96
- 平均合併
- 15 小時 20 分鐘
- 30 天內合併 PR
- 3
描述
I am using the library as shown below and I am flooded from logs coming from the library:
2025-02-11 17:17:37,072 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,119 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,199 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,249 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,330 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,391 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,470 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,516 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,591 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,641 - INFO - ClientSecretCredential.get_token succeeded
How do I make it stop?
async def find_user(client: GraphServiceClient, user_id: str) -> None:
query_params = UserItemRequestBuilder.UserItemRequestBuilderGetQueryParameters(
expand = ["manager($levels=max;$select=id,displayName,mail,department,jobTitle)"],
select = ["customSecurityAttributes","id","displayName","mail","department","jobTitle"],
)
request_configuration = RequestConfiguration(
query_parameters = query_params,
)
return await client.users.by_user_id(user_id).get(request_configuration = request_configuration)
Originally posted by @Marcuccio in https://github.com/microsoftgraph/msgraph-sdk-python/discussions/1112
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從提供的 find_user 進入點開始,使用 GraphServiceClient 和所示的請求設定重現重複的資訊輸出。追蹤發出 HTTP 和認證資訊訊息的程式庫元件;當請求在沒有過多資訊記錄的情況下仍能正常運作,且該行為由適當的迴歸檢查涵蓋時,即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- api, backend
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 35/100