Opening a notebook in a codespace
See original GitHub issue- open a
ipynb
file in a codespace ->
Issues:
- ~python extension activation shows the welcome page stealing the focus from the notebook that I opened~ //cc @brettcannon
- ~I get immediately asked for a survey~
- the kernel port gets forwarded (this is a missing API adoption, @alexr00 has the details)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Getting started with GitHub Codespaces for machine learning
You can open your codespace in JupyterLab from the "Your codespaces" page at github.com/codespaces, or by using GitHub CLI. For more information, see...
Read more >Using Codespaces with JupyterLab (Public Beta)
Using GitHub Codespaces with JupyterLab combines the delightful notebook editing, data exploration, and narrative building experiences of ...
Read more >Jupyter Notebooks in GitHub Codespaces - DEV Community
Very easy to set up and use. Really like the 'show (notebook) variables' option in "locally" connected Jupyter notebook. There is also the ......
Read more >How to Execute Jupyter Notebooks from GitHub
Currently, you may sign up for beta access to Codespaces, which will include some free compute to run your notebooks on. Codespaces Open...
Read more >First look at GitHub Codespaces - NillsF blog
I have a notebook I use for my own personal covid analysis. I copy-pasted that notebook into the codespace, restarted the codespace (i.e....
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 FreeTop 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
Top GitHub Comments
@alexr00 sorry i missed ur comment. It was very easy to use (didn’t have to look at any existing code to figure it out).
Good question, let me look into this. The problem is these ports are opened by other packages & executables (& in 99% of the case we don’t even know the CLI ahead of time)
@DonJayamanne Yes, for ports that the extension knows about and are internal to the working of the extension, use
PortAutoForwardAction.ignore
. For ports that the extension doesn’t know about, simple exclude them from your returned array of attributes. If there are any ports that the extension knows about but are external to the working of the extension, i.e. user facing, you can returnPortAutoForwardAction.notify
if you want to make sure that the user is notified, or you can simply leave them out of your returned array and let the user’s settings handle whether they get notified.