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
Logs generated during loading of extensions are not output #1958
Comments
They work fine for me, we handle this in It is mostly |
I set from pprint import pprint
pprint(_delayed_handler._buffer) |
I've just done exactly this (snippet below) for both config files and tried both the service and also running as my user on the command line, and I'm afraid I still can't reproduce this. Also, looking at the Mopidy code, I also can't explain why your above snippet wouldn't print a bunch of the delayed log statements, can you?
Is it just the
|
I don't see the version log message either. The first debug log messages I see with
The first non-debug log message I see is the list of enabled extensions:
I'm this running on python3.8 as an unprivileged user manually from the CLI with the following invocation:
|
Probably also worth mentioning that I'm running this inside of a virtualenv that was created like so:
|
I've found the issue, and will have a PR ready shortly. |
In the latest release, the logs generated by
mopidy.ext.load_extensions()
are not output anywhere. From what I can tell, this is because that function is called before logging is set up further down themain()
function.This makes it very difficult to diagnose issues related to individual extensions not being loaded. I'm trying to revive the API Explorer extension and found this while trying to get it to load.
The text was updated successfully, but these errors were encountered: