Hi! while using vscode on Orchest cloud, I am not able to see option for running the cell.
09/25/2021, 5:42 PM
Hi Sumit! I totally understand your confusion.
The fact that vscode is not displaying an option to run the cell is probably because there is no kernel attached to the Notebook. It is just an editable view of the Notebook. I hope that explains things.
If you want to run the Notebooks by running individual cells, then you will have to use the integrated JupyterLab.
@Rick Lamers Do you think there is something we can do here to make Notebook running through VSCode possible? Shouldn’t be too hard in case they support connecting to the enterprise gateway
09/25/2021, 5:47 PM
We can investigate, but it’s not recommended to use notebooks in VS Code at the moment.
09/26/2021, 4:56 AM
Hi @Yannick, that explains things. Thanks! It would be great if we could use Notebooks in VS Code.
@Rick Lamers are there any downsides of using Notebooks in VS Code? I have been using them for quite a while and sometimes it behaves weirdly (like running wrong cells, not being able to copy output of cells) but once you restart the editor it works fine. As the benefits outweigh the cons I am still using it. Let me know if there are any known major issues.
09/26/2021, 8:44 AM
Hi Sumit, it has to do with kernel connection but also with versioning. We promote versioning a source code version of notebooks using jupytext. The VS Code ecosystem to support kernel gateways and/or source code based versioning is much less mature today.
The kernel gateway setup is what allows your kernels to actually run in the container environment that’s defined by the Orchest Environment. In normal language, it’s what makes it possible to handle code dependencies (pip/apt) in Jupyter kernels cleanly.