[Feature] 优化log输出
- Dominant language
- Python
- Stars
- 485
- Forks
- 81
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 8
Description
**Problem Statement**
把集成测试的trace输出改成log_level改成info
```
2025-11-30 23:04:38,030 DEBUG _trace.py:87 -- connect_tcp.complete return_value=
2025-11-30 23:04:38,031 DEBUG _trace.py:87 -- send_request_headers.started request=
2025-11-30 23:04:38,031 DEBUG _trace.py:87 -- send_request_headers.complete
2025-11-30 23:04:38,031 DEBUG _trace.py:87 -- send_request_body.started request=
2025-11-30 23:04:38,031 DEBUG _trace.py:87 -- send_request_body.complete
2025-11-30 23:04:38,031 DEBUG _trace.py:87 -- receive_response_headers.started request=
2025-11-30 23:04:38,043 DEBUG _trace.py:87 -- receive_response_headers.complete return_value=(b'HTTP/1.1', 200, b'OK', [(b'date', b'Sun, 30 Nov 2025 15:04:37 GMT'), (b'server', b'uvicorn'), (b'content-length', b'572'), (b'content-type', b'application/json')])
2025-11-30 23:04:38,043 INFO _client.py:1740 -- HTTP Request: GET http://127.0.0.1:52451/apis/envs/sandbox/v1/get_status?sandbox_id=85ec0edd5f9b40c3b2d60a884e2257d8 "HTTP/1.1 200 OK"
2025-11-30 23:04:38,043 DEBUG _trace.py:87 -- receive_response_body.started request=
2025-11-30 23:04:38,043 DEBUG _trace.py:87 -- receive_response_body.complete
2025-11-30 23:04:38,043 DEBUG _trace.py:87 -- response_closed.started
2025-11-30 23:04:38,043 DEBUG _trace.py:87 -- response_closed.complete
2025-11-30 23:04:38,044 DEBUG _trace.py:87 -- close.started
2025-11-30 23:04:38,044 DEBUG _trace.py:87 -- close.complete
```
**Proposed Solution**
**Detailed Feature Description**
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the integration tests and the _trace.py log output shown in the report. Find where the trace logger level is configured, then verify the resulting integration-test output uses info rather than debug for these trace messages. Done means the integration tests produce the intended log level without the listed DEBUG entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100