Excessive Informational Logs from Library During HTTP Requests
还没有人认领这个 Issue。
评估
调研方向
从提供的 find_user 入口点开始,使用 GraphServiceClient 和所示的请求配置重现重复的信息输出。跟踪发出 HTTP 和凭据消息的库组件;当请求在没有过多信息日志的情况下仍能正常工作,并且该行为由适当的回归检查覆盖时,即视为完成。
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- Python
- 星标
- 630
- 派生
- 96
- 平均合并
- 15 小时 20 分钟
- 30 天内合并 PR
- 3
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoftgraph/msgraph-sdk-python 的其他 Issue
-
status:waiting-for-triage type:bug
难度 1/5 1 小时以内 新手友好度 90/100
microsoftgraph/msgraph-sdk-python#1570 ·
-
status:waiting-for-triage type:bug
难度 2/5 1-3 小时 新手友好度 75/100
microsoftgraph/msgraph-sdk-python#1563 ·
-
Needs: Attention :wave: type:bug
难度 2/5 1-3 小时 新手友好度 62/100
microsoftgraph/msgraph-sdk-python#1287 · 2 条评论 · 1 个 reaction ·
-
status:waiting-for-triage type:bug
难度 3/5 1-2 天 新手友好度 52/100
microsoftgraph/msgraph-sdk-python#1578 ·
-
status:waiting-for-triage
难度 5/5 一周以上 新手友好度 25/100
microsoftgraph/msgraph-sdk-python#1557 ·
查看 microsoftgraph/msgraph-sdk-python 的全部 Issue
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 70/100
canonical/paas-charm#368 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
-
tech debt
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 1/5 1 小时以内 新手友好度 90/100
StevenBlack/hosts#3256 ·
-
难度 1/5 1 小时以内 新手友好度 90/100
qualcomm/qai-appbuilder#275 ·