question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Language server warnings

See original GitHub issue

Description

After installing the 3.8 version along with jupyter-lsp 1.4.0, new server warnings are logged when running jupyterlab in the format:

Failed to validate commands from language server spec finder `x-language-server`: [<ValidationError: "None is not of type 'string'">]

for some of the language server specs defined here (See list below) Command Line Output:

[W 2021-07-06 12:28:01.705 ServerApp] Failed to validate commands from language server spec finder `bash-language-server`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.705 ServerApp] Failed to validate commands from language server spec finder `dockerfile-language-server-nodejs`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.706 ServerApp] Failed to validate commands from language server spec finder `javascript-typescript-langserver`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.708 ServerApp] Failed to validate commands from language server spec finder `pyright`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.710 ServerApp] Failed to validate commands from language server spec finder `sql-language-server`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.712 ServerApp] Failed to validate commands from language server spec finder `unified-language-server`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.712 ServerApp] Failed to validate commands from language server spec finder `vscode-css-languageserver-bin`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.713 ServerApp] Failed to validate commands from language server spec finder `vscode-html-languageserver-bin`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.713 ServerApp] Failed to validate commands from language server spec finder `vscode-json-languageserver-bin`:
    [<ValidationError: "None is not of type 'string'">]
[W 2021-07-06 12:28:01.714 ServerApp] Failed to validate commands from language server spec finder `yaml-language-server`:
    [<ValidationError: "None is not of type 'string'">]

I believe this is be related to troubleshooting introduced in #634 where a new property is added to the schema but some of the server language specs are not including it.

Reproduce

  1. Install jupyterlab (3.0.14)
  2. Install jupyterlab-lsp (3.8.0) and jupyter-lsp (1.4.0)
  3. Run jupyter lab with the --debug flag and watch for warning logs

Expected behavior

Either no warnings logged for missing servers, or a way to turn them off?

Context

  • Operating System and version: MacOS Version 11.3.1
  • Browser and version: Chrome Version 91.0.4472.114
  • JupyterLab version: 3.0.14
Required: installed server extensions
    jupyter_lsp enabled
    - Validating jupyter_lsp...
      jupyter_lsp 1.4.0 OK
    jupyterlab enabled
    - Validating jupyterlab...
      jupyterlab 3.0.14 OK
    nbclassic enabled
    - Validating nbclassic...
      nbclassic  OK
Required: installed lab extensions
JupyterLab v3.0.14
my-conda-env/share/jupyter/labextensions
        bqplot v0.5.26 enabled OK (python, bqplot)
        @krassowski/jupyterlab-lsp v3.8.0 enabled OK (python, jupyterlab-lsp)
        @jupyter-widgets/jupyterlab-manager v3.0.0 enabled OK (python, jupyterlab_widgets)

Other labextensions (built into JupyterLab) app dir: my-conda-env/share/jupyter/lab

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
karlaspuldarocommented, Jul 8, 2021

I can help looking into this

1reaction
krassowskicommented, Jul 8, 2021

Thank you. We need to improve the validator output as it is hard to tell what failed from these logs, but I believe your assessment right. An immediate solution is could be to update the schema to accept null for troubleshoot. I agree that ideally we would not be showing warnings for servers which are not installed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

python-language-server/TROUBLESHOOTING.md at master
Unresolved import warnings​​ The language server treats the workspace root (i.e. folder you have opened) as the main root of user module imports....
Read more >
Language Server Protocol Specification - 3.17
This document describes the 3.17.x version of the language server protocol. ... Represents a diagnostic, such as a compiler error or warning.
Read more >
Language Server Extension Guide - Visual Studio Code
Learn how to create Language Servers to provide rich language features in Visual Studio Code. ... Warning, range: { start: textDocument.
Read more >
Language Server Protocol - Wikipedia
The Language Server Protocol (LSP) is an open, JSON-RPC-based protocol for use between ... and marking of warnings and errors, as well as...
Read more >
language server, viewing errors : r/vim - Reddit
I have the language server set up, for Rust, and I can see Red "E>" symbols popping up on the left side of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found