-
Notifications
You must be signed in to change notification settings - Fork 52
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
CondaStoreServer.log_level doesn't do anything #516
Comments
If this is not used, and it is otherwise not adding anything in terms of user experience (CLI use) would it not be best to remove this altogether? |
@costrouc @pierrotsmnrd - What do you think about this? |
@costrouc last ping here. Otherwise will just move ahead with removing this altogether. |
I think this is a worthwhile issue to look into since this is the primary way that we debug things within a kubernetes deployment on nebari. I'd also say logging/printing in conda-store-server/worker(s) is inconsistent and needs clean up. Traitlets does provide a log attribute to LoggingConfigurable classes but it is not always accessible where you need. |
@nkaretnikov can you please take on this issue? |
Closed by #940. |
CondaStoreServer.log_level
nominally controls the logger level (see https://conda.store/en/latest/administration.html#conda-store-server-server-app-condastoreserver), but it's never actually used anywhere.Furthermore, the log level is difficult to set at the command line because
--CondaStoreServer.log_level=DEBUG
doesn't work. You'd have to use--CondaStoreServer.log_level=10
(wherelogging.DEBUG == 10
).The text was updated successfully, but these errors were encountered: