Log level for jupyterlab-lsp <-> pygls setting?
See original GitHub issueWith 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.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
pygls logging level INFO in terminal that launches JupyterLab ...
Thanks for looking into this. I can confirm with the log level set to WARN in cli.py no flood of messages appear in...
Read more >Advanced Usage — pygls documentation - Read the Docs
Official documentation about logging in python can be found here. Below is the minimal setup to setup logging in pygls: import logging from...
Read more >jupyterlab-lsp - Bountysource
Is there a way to see the complete message exchange between LS and Jupyter? The console output via 'Language Server Setting -> loggingLevel:...
Read more >Change level logged to IPython/Jupyter notebook
One, which is set in the ipython_notebook_config file, only affects the internal IPython logging level. The other is the IPython logger, ...
Read more >Enabling Type Checking on Columns in Data Frame Libraries ...
rather than supported at the language level, it is hard to find out errors due ... the type of data frame objects as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.https://github.com/pappasam/jedi-language-server/issues/186#issue-1079266541