Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remote.ssh: suppress paramiko logging #3675

Merged
merged 2 commits into from
Apr 29, 2020

Conversation

pmrowla
Copy link
Contributor

@pmrowla pmrowla commented Apr 24, 2020

  • ❗ I have followed the Contributing to DVC checklist.

  • πŸ“– If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here. If the CLI API is changed, I have updated tab completion scripts.

  • ❌ I will check DeepSource, CodeClimate, and other sanity checks below. (We consider them recommendatory and don't expect everything to be addressed. Please fix things that actually improve code or fix bugs.)

Thank you for the contribution - we'll try to review it as soon as possible. πŸ™

Will close #3482.

paramiko is loaded lazily, so the paramiko logger is not suppressed in dvc/logger.py::disable_other_loggers(). This leads to paramiko emitting expected error messages when we hit the max SFTP channel limit, even though it is not an error condition for DVC. The logger should just be suppressed when we load paramiko, since any actual SSH/SFTP errors will be caught and logged as DvcExceptions.

@pmrowla pmrowla self-assigned this Apr 24, 2020
@pmrowla pmrowla requested review from efiop and skshetry April 24, 2020 06:20
dvc/remote/ssh/connection.py Outdated Show resolved Hide resolved
dvc/remote/ssh/connection.py Show resolved Hide resolved
@skshetry skshetry merged commit 31fe778 into iterative:master Apr 29, 2020
@pmrowla pmrowla deleted the 3482-paramiko-logger branch April 29, 2020 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Secsh channel 10 open FAILED: open failed: Connect failed
3 participants