Cannot change log level

[drammock]

Description

This extension generates more than 100 lines of build output in my terminal, which makes it harder to find other output that I'm more interested in (e.g. sphinx warnings). I want to set the log level somehow, but can't figure out how. I have placed a jupyterlite_config.json in the same directory as conf.py and it's getting loaded:

[LiteBuildApp] Loaded config file: /opt/pydata-sphinx-theme/docs/jupyterlite_config.json

Here's the content of that file:

{
    "LiteBuildConfig": {
        "Application": {
            "log_level": 40
        }
    }
}

Inspired by this I also tried

{
    "LiteBuildConfig": {
        "log_level": 40
    }
}

but that gives a warning:

[LiteBuildApp] WARNING | Config option `log_level` not recognized by `LiteManager`.

Any guidance on how to actually suppress the terminal output of LiteBuildApp?

Reproduce

Sorry this is a complicated reproducer, I haven't had time to boil it down:

• clone https://github.com/drammock/pydata-sphinx-theme/tree/silence-warnings
• install nox
• run nox -s docs
• see the 100+ lines of LiteBuildApp output in the terminal that is not getting suppressed.

Expected behavior

the 100+ lines of output will be suppressed

Context

$ mamba list jupyterlite
# packages in environment at /opt/mambaforge/envs/pst:
#
# Name                    Version                   Build  Channel
jupyterlite-core          0.1.3              pyhd8ed1ab_0    conda-forge
jupyterlite-sphinx        0.9.3              pyhd8ed1ab_0    conda-forge
$ uname -a
Linux agelaius 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Browser: N/A, this is about terminal output during build

[Carreau]

I believe this was taken care of by #153

[steppi]

I believe this was taken care of by #153

Right. @drammock, what we found is that jupyterlite has unprotected print statements and doesn't allow for setting a log level. The solution we came up with was to make it the default to silence all output from `jupyterlite`` but to offer an option to un-silence the output.

[agriyakhetarpal]

@steppi, would it be a good idea to add a three-level (or less) logger and configure it? I feel it can be taken up in #162

[steppi]

@steppi, would it be a good idea to add a three-level (or less) logger and configure it? I feel it can be taken up in #162

There's some prep work needed for that to actually help because the vast majority of noisy output comes upstream and can't be controlled with a logger.

Some of the output comes for doit from within jupyterlite_core, the verbosity is hard coded, and we'd need to get them to allow this to be configured. See jupyterlite/jupyterlite#1351.

Another source of noisy output is unguarded print statements in jupyterlite_core/addons/ as described in #149 (comment). These would need to be changed to use a logger.

If we actually want the log level to be configurable, this stuff needs to be changed upstream.