New platform-dependent `%launch_viz` line magic
See original GitHub issueIdeal outcome:
- make new
%launch_viz
line magic in kedro-viz, so that in any notebook with kedro IPython extension loaded,%launch_viz
will be available %launch_viz
starts a kedro-viz server and supplies a URL which the user can click on to open kedro-viz in another browser window
Required steps:
- Make sure the current code is still the best way to launch the server from inside the line magic
- Potentially difficult. Work out the correct URL to access the kedro-viz instance on various platforms (databricks, sagemaker, etc.).
- Potentially difficult. Work out how to programmatically obtain this URL
- Work out how to automatically figure out which platform the notebook is running on
- Output the correct URL or some useful message which might help a user find their kedro-viz instance if we can’t figure out the URL ourselves
To consider:
- how/which arguments can the user pass? Ideally all the same flags as used when you do
kedro viz
would be available the same way - how to kill the server? See note in https://github.com/kedro-org/kedro/pull/1355 for current bug with
%run_viz
where this doesn’t happen
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
No results found
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
How to efficiently develop with Kedro-Viz on Databricks
After much trial and error, I have come up with a much more streamlined way to iterate on code being developed for Databricks. This should help to make the development loop much faster since there’s no need to restart the cluster or manually handle repos this way 🎉
make build
,git add -f package/kedro_viz/html
and push to GitHub. This is temporarily needed while developing on your branch so that you canpip install
from GitHub but should not remain there when you merge tomain
kedro-viz
andkedro
are not installed as cluster libraries.NAME-OF-BRANCH
):pip install
the latest changes to the branch directly from GitHub. No need to restart the cluster or clone repos any more.package/kedro_viz/html
folder before merging tomain
.Let’s assume there will be two different ways that
%launch_viz
would work:Next steps:
%launch_viz
that starts process and links to it (find out if there’s a programmatic way to get the URL through jupyter-server-proxy)%launch_viz
to take arguments for--pipeline
etc.kedro viz --autoreload
; need to think about how to get project path there)