Log level for jupyterlab-lsp <-> pygls setting?

With the jupyterlab-lsp (3.9.1) on Jupyterlab (3.2.4, Windows) activated my console is flooded with messages from the pygls module:

INFO:pygls.protocol:Sending data: {"jsonrpc": "2.0", "id": 0, "result": {"capabilities": {"textDocumentSync": {"openClose": true, "change": 2, "willSave": false, "willSaveWaitUntil": false, "save": true}, "completionProvider": {"triggerCharacters": [".", "'", "\""], "resolveProvider": true}, "hoverProvider": true, "signatureHelpProvider": {"triggerCharacters": ["(", ","]}, "definitionProvider": true, "referencesProvider": true, "documentHighlightProvider": true, "documentSymbolProvider": true, "codeActionProvider": {"codeActionKinds": ["refactor.inline", "refactor.extract"]}, "renameProvider": true, "executeCommandProvider": {"commands": []}, "workspaceSymbolProvider": true, "workspace": {"workspaceFolders": {"supported": true, "changeNotifications": true}, "fileOperations": {}}}}}
INFO:pygls.protocol:Sending data: {"jsonrpc": "2.0", "id": 1, "result": null}
INFO:pygls.protocol:Sending data: {"jsonrpc": "2.0", "id": 2, "result": null}
INFO:pygls.protocol:Sending data: {"jsonrpc": "2.0", "id": 3, "result": null}
INFO:pygls.protocol:Sending data: {"jsonrpc": "2.0", "id": 4, "result": null}
[...]

As far as I can see with the current settings of the juypterlab-lsp the log level should be much stricter:

    // Log all LSP communication with the LSP servers
    // Whether all messages sent to and received from LSP servers should be logged into the console. To see these messages, set loggingLevel to debug or log. Note: Only messages handled by the new API will be shown.
    "logAllCommunication": false,

    // Logging console type
    // The console to use for debugging problems with this extension. Allowed values are: browser, floating.
    "loggingConsole": "browser",

    // Logging console verbosity level
    // The verbosity of the console for debugging problems with this extension. Allowed values are: debug, log, warn, error.
    "loggingLevel": "warn",

Is there a separate setting to suppress this flood of messages? Otherwise the console becomes unusable.

[krassowski]

Closing, as the verbosity setting was improved upstream in https://github.com/pappasam/jedi-language-server/pull/188 and new version of jedi-language-server is now available. If you are seeing this problem please upgrade jedi-language-server to v0.35.0 or newer.

[selasley]

https://github.com/pappasam/jedi-language-server/issues/186#issue-1079266541