Hard-coded DEBUG log level in SFTPServer start_subsystem
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.9k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
Is there a reason why the logging for caught Exceptions in paramiko/sftp_server.py:SFTPServer.start_subsystem is done as DEBUG and not as at least WARNING?
For example here:
https://github.com/paramiko/paramiko/blob/master/paramiko/sftp_server.py#L105
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in paramiko/sftp_server.py at SFTPServer.start_subsystem and inspect the caught-Exception logging near line 105. Check the surrounding logging behavior and determine whether the issue is resolved by changing the level from DEBUG to WARNING or by documenting the existing choice; done means the handling matches the project’s intended severity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100