Michał Krassowski

It would probably be good if you could take a look at the discussion in #600 and at the trimmed draft in https://github.com/jupyterlab/jupyterlab/pull/10523 to provide a feedback from your perspective.

> Regarding timeline/upstreams: are we thinking this will target jupyterlab 3 and retrolab, or should we be shooting more for lab4/notebook7? I would currently aim to release it with 3.3,...

Thanks for the interest! If your widget implements `IDocumentWidget` interface, and you have a tracker implementing `IWidgetTracker` interface you could re-use the registration code linked below: https://github.com/jupyter-lsp/jupyterlab-lsp/blob/0cff6b9cd7dab4d44f877cf7bacc91bf72c6ec4e/packages/jupyterlab-lsp/src/adapters/file_editor/index.ts#L1-L43 I think we...

Thanks for asking. I don't see anything concerning in the screenshots you shared so far (other than using sudo which hints at using a global environment which can lead to...

I would just recommend to uninstall `pyls` or `pylsp` - there is no point in having both installed.

This is likely a bug in pylsp / some other package writing out to standard output. We should add a try-catch to be able to better debug these issues. In...

Could you please try again, but instead of `print(e)` use `print(line)`? It is not related to any specific browser, this is a problem on the backend.

It's `pyls-memestra`. It used to have a line printing: `print("pyls_lint 🐔")`, [now commented out](https://github.com/QuantStack/pyls-memestra/blob/1df3f91a2718f497dd9719b5775a7d66d79e78c9/pyls_memestra/plugin.py#L32) which was fixed three months ago by https://github.com/QuantStack/pyls-memestra/pull/51. I commented https://github.com/QuantStack/pyls-memestra/pull/51#issuecomment-1003365375 at the time that this...

I changed the title and labelled it as an enhancement, as we could do a better job at surfacing the faulty line when something goes wrong. Thank you for reporting...

Thanks for the confirmation. I will reopen this issue to keep track of the improvement.