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.

Sign up for GitHub

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

Jump to bottom

Logging.conf files left behind by iotsaControl #43

Closed
jackjansen opened this issue Jan 8, 2021 · 0 comments
Closed

Logging.conf files left behind by iotsaControl #43

jackjansen opened this issue Jan 8, 2021 · 0 comments
Assignees
@jackjansen

Comments

@jackjansen
Copy link
Contributor

jackjansen commented Jan 8, 2021 •
edited
Loading

Whenever you run iotsaControl anywhere it leaves a logging.conf file behind. And DEBUG logging is always enabled for all modules that use the Python logger...

The culprit is CoAPthon, the COAP module. A bug has been filed there, Tanganelli/CoAPthon#162, but no reaction by the author over the last 6 months.

The problem is also experienced another user of CoAPthon, see rgerganov/py-air-control#55

They have already forked CoAPthon. Maybe use their fork (until and if the original is fixed).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jackjansen jackjansen

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jackjansen