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

quads-cli leaks some logging into stdout #250

Closed
sadsfae opened this issue May 22, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@sadsfae
Copy link
Member

commented May 22, 2019

There seems to be some leaking of Python logging into quads-cli output.

quads-cli --ls-schedule --host f19-h07-000-r620.rdu2.example.com
2019-05-22 17:07:35,860 Starting new HTTP connection (1): 127.0.0.1:8080
2019-05-22 17:07:35,867 http://127.0.0.1:8080 "GET /api/v2/cloud HTTP/1.1" 200 8540
2019-05-22 17:07:35,872 http://127.0.0.1:8080 "GET /api/v2/host?name=f19-h07-000-r620.rdu2.example.com HTTP/1.1" 200 702
Default cloud: cloud02
2019-05-22 17:07:35,883 http://127.0.0.1:8080 "GET /api/v2/current_schedule?host=f19-h07-000-r620.rdu2.example.com HTTP/1.1" 200 220
Current cloud: cloud02
2019-05-22 17:07:35,888 http://127.0.0.1:8080 "GET /api/v2/schedule?host=f19-h07-000-r620.rdu2.example.com HTTP/1.1" 200 220
1| start=2019-05-20 22:00:00, end=2019-06-16 22:00:00, cloud=cloud02

@sadsfae sadsfae added this to the 1.1.0 milestone May 22, 2019

@grafuls

This comment has been minimized.

sadsfae pushed a commit that referenced this issue May 23, 2019

Fix for leaking logging.
Turns out for some reason quads-cli inherits log properties from
move and rebuild.

Fixes: #250
Change-Id: Iafdc551809a3ce14696e0f240464b642f3c3389e

@sadsfae sadsfae closed this May 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.