Rename project about dask-labextension HOT 24 CLOSED

Repo and python package jupyterlab_dask.

from dask-labextension.

cf https://github.com/jupyterlab/jupyterlab_geojson

from dask-labextension.

Ok. So how would we like to do this? Rename the repo or create a new one?

from dask-labextension.

This repository is, as far as I understand, quite out of date with newer JLab conventions. It would be entirely acceptable to change it's name. We would first want to verify that it still has valuable contents.

from dask-labextension.

Yeah that's what I gathered. So part of the reason I ask is I'm interested in refreshing it. Though admittedly I don't know all of what is needed to do that. So maybe @blink1073 can advise. 😉

Admittedly seeing a more stable JupyterLab would help motivate me, but it looks like a stable beta is a few weeks off. Being able to have the dashboard live alongside a running notebook is pretty desirable too. 😄

from dask-labextension.

I agree that that would be pretty great. This extension needed some work before, I think, it would be very useful. In particular it would be handy to be able to point to a scheduler address running somewhere remotely. Perhaps there is a way that the Client's repr on the screen could hold this information and we could drag it to some new panel? I think that currently this is hard-coded to look at localhost:8787

from dask-labextension.

I see. Yeah being able to configure the Client somehow would be good. Maybe there's a good example extension, which allows configuring its settings somewhere?

Do you remember any other todos?

from dask-labextension.

I think that once a connection was made it was hard to remake a different connection (for example if the scheduler went down and came back up). Generally both this and the comment above point to a need within this project to manage connections to the scheduler. This might be a different JLab panel, or we might be able to take queues from a notebook. I got the sense that this was pretty easy to do for someone who has familiarity with JLab, but I'm not sure.

from dask-labextension.

@jakirkham, our walkthrough extension is here, but doesn't yet have settings (which are changing a bit in jupyterlab/jupyterlab#3167). An example core extension that uses settings is the file editor: schema, usage.

from dask-labextension.

Do you think this area of JupyterLab is more stable now, @blink1073? I'd be interested in getting Dask working with JupyterLab, but probably can't devote lots of time to it. So it would really help to know if this is a moving target or not to determine whether I should wait a little longer or start playing.

from dask-labextension.

Hi @jakirkham, I'd say wait for the next beta release. I have a goal to get most of the JS packages to 1.0 for that release, which will make maintaining extensions much easier.

from dask-labextension.

Sounds good. Is there somewhere I should be listening to know when it is ready or would you be able to update me here?

from dask-labextension.

We'll be making an announcement on the Jupyter mailing list.

from dask-labextension.

@jasongrout, do you have any advice on how to create a lab extension for this use case these days? Tried to look at the example link in this comment, but it appears to be broken. Also there is the open question of the best way to add settings to it.

from dask-labextension.

how to create a lab extension for this use case

Is 'this use case' an extension that uses settings?

CC also @afshin, @ian-r-rose who both have written either the settings system or extensions that dealt with the settings system.

from dask-labextension.

The use case is showing the Dask Distributed dashboard. The primary setting would be specifying the IP and port for connecting to the web server hosting this dashboard.

Now that we are discussing this, vaguely remember Matt mentioning the possibility of breaking up the dashboard into various panels that could be laid out around a running notebook. Expect this would also be interesting to users, who want to track multiple activity streams (resource utilization, task scheduling/completion, etc.) while running their code.

from dask-labextension.

from dask-labextension.

from dask-labextension.

from dask-labextension.

So I've used jupyterlab sidecar with some success for this. There are some general resize rendering issues but it's tolerable

from dask-labextension.

from dask-labextension.

Are we still interested in renaming or should this be closed?

from dask-labextension.

I think the name is fine as is. As long as it has been published with the relevant keywords it should be discoverable

from dask-labextension.

We seem to have settled on dask-labextension. Closing.

from dask-labextension.