The only error came from another kernel client interacting with the same kernel, which caused such error to be reported via the ioPub channel. I just noticed, that the running of all cells stopped, although there was no error in the execution of cells and usually it only stops if there is an error. Like I said, only a hunch, and I have not yet had the chance to make a test setup for this, to be sure. It might be the case, that JupyterLab needs an additional check for the session id / kernel client id somewhere, to distinguish between errors of normal cell execution and errors stemming from other client's interactions with the same kernel. If someone clicks "run all cells" for example, I have a hunch (but no proof yet, but still a think this might be happening), that the execution of further cells does not happen, because of such errors, even though the execution of the cells themselves did not cause that error. The extension interacts with the current kernel, as said before, but it can also cause Python errors to happen, during that interaction. I also have made another observation, working on that extension I am building. Any pointers where to start? What is the best place to open a new issue? jlab-image-editor: Simple image editor for JupyterLab. However, I would like to either fix the extension or labextension build command, so this error does not happen. jupyterlab-topbar-text: JupyterLab extension to display arbitrary text in the top bar. Jupyterlab autocomplete extension install#If I remove the object, run the build command and then manually add the object back to the compiled extension source, I am able to install and use the extension. I also tracked the issue down to the particular object created by the extension. Is there any way to debug what's happening during jupyter labextension build? (node:108) DeprecationWarning: Compilation.cache was removed in favor of Compilation.getCache() " However, the second command hangs for unknown reason with the following output $ tsc & jupyter labextension build -development True. The build command is effectively replaced from "tsc" to "tsc & jupyter labextension build -development True. I am trying to use the new development scripts in package.json (as described in ). Jupyterlab autocomplete extension update#Hi, I have another extension-related question to you all: I am trying to update jupyterlab-latex to enable new build system and I am hitting few different issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |