Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Tim Paine
@timkpaine
lookin at jupyterlab/jupyter-renderers#3
Tim Paine
@timkpaine
I suppose I can just bundle in lumino, since we won't have the same issue with multiple lumino version on the page that we have in jlab?
Max Klein
@telamonian
@timkpaine I think we're going to need some more details
Yuvi Panda
@yuvipanda
are there any code samples on how to use react inside jupyterlab?
I see https://jupyterlab.readthedocs.io/en/stable/developer/virtualdom.html but no code
to go back, all I'm trying to do is to have a dropdown + another component inside a component
I know how to do this with plain DOM, or with react
trying to find out how I would with JupyterLab
Jeremy Tuloup
@jtpio
@yuvipanda maybe this? https://github.com/jupyterlab/extension-examples/tree/master/react/react-widget
Yuvi Panda
@yuvipanda
@jtpio Looks like exactly what I needed! Thank you
Jeremy Tuloup
@jtpio
do you think this should be made more visible in the docs? for now there is a link to the repo on the latest version of this page: https://jupyterlab.readthedocs.io/en/latest/developer/extension_dev.html
Yuvi Panda
@yuvipanda
@jtpio I think it should be in https://jupyterlab.readthedocs.io/en/latest/developer/virtualdom.html. Also, I see there's a bunch of 'literalinclude' with code snippets that aren't present in the rendered output
IMO that would've been of big help
@jtpio works on my local build but not on RTD, latest or stable
@jtpio I filed jupyterlab/jupyterlab#8473
Jeremy Tuloup
@jtpio
do you have a screenshot of what it looks like locally?
Yuvi Panda
@yuvipanda
@jtpio I pasted in the issue
Jeremy Tuloup
@jtpio
:thumbsup:
Yuvi Panda
@yuvipanda
@jtpio actually to step back - all I wanna do is to have a dropdown above another Lumino component as the children of my widget. I can't figure out at all how to do that with Lumino. Can you help / have pointers?
This feels like it should be fairly simple but I've not found anything at all in the docs
Jeremy Tuloup
@jtpio
with the child Lumino component updating when the value of the dropdown changes?
Yuvi Panda
@yuvipanda
@jtpio yeah, some code needs to be triggered
actually I think I can just take lumino out of the equation completely and go pure react
there isn't really any lumino need there
Jeremy Tuloup
@jtpio
maybe the cell type dropdown in the notebook toolbar can be useful as reference: https://github.com/jupyterlab/jupyterlab/blob/b62d4fd463c6d00451df6327203413cf1b520a8f/packages/notebook/src/default-toolbar.tsx#L243-L308
Yuvi Panda
@yuvipanda
oooh nice, I didn't know that was react now!
I like it
Jeremy Tuloup
@jtpio
yes there is a bit of react in some places in core
Naveen Michaud-Agrawal
@nmichaud
@jtpio any thoughts on moving the ReactWidget into lumino proper? Seems it would be useful outside of jupyterlab
also looks like it doesn't depend on anything within JupyterLab itself
Jeremy Tuloup
@jtpio
@nmichaud maybe worth asking on the lumino channel or in a new issue?
otherwise it should be possible to import from apputils in standalone applications outside of jupyterlab with import { ReactWidget } from '@jupyterlab/apputils';
Yuvi Panda
@yuvipanda
how do I set the min-width of my sidebar? css doesn't seem to work because width setup is in JS?
Yuvi Panda
@yuvipanda
also just wanted to say y'all are pretty awesome. I know I can be very cranky and unappreciative sometimes, acting as an entitled user. I'm sorry, and <3
Steven Silvester
@blink1073
Hi Yuvi, we're all cranky these days. 😀. I think what you're seeing is CSS specificity, the width is set on the sidebar id. You can add the property with the !important modifier or use a more specific rule
Afshin Taylor Darian
@afshin
!important is a hammer ... yeah maybe you need it, but a more specific rule always plays nicer with others and with the future ... if the option exists!
Steven Silvester
@blink1073
:hammer: :clock: oh woah woah woah woah
ha, that's what I get for trying to type that on a phone
(hammer time)
Afshin Taylor Darian
@afshin
:joy:
Marc Allen
@mc-allen
Hi everyone, I'm running into an issue with extensions that I was hoping someone has a suggestion.
I am running jupyterlab inside a docker container, where I pre-install jupyterlab and all of the extensions as root user. When I run the docker container, I am running as a different user. In this case, the extensions fail to load in jupyterlab because the NPM cache folder is read-only for the current user, with "[...] are not valid NPM packages."
This is actually happening because jupyterlab calls "npm pack" on the extensions, requiring r/w access to the cache. If I chmod the cache first, everything works.
Is there a way to run jupyterlab where this wouldn't be an issue, i.e. it doesn't require r/w access to the original npm cache (that is owned by root on my system)?
Chris Holdgraf
@choldgraf
In case y'all are interested in this, there's a poll out there on twitter about people's preferred jupyter interface: https://twitter.com/betatim/status/1265591840939610113
Yuvi Panda
@yuvipanda
@afshin @blink1073 awesome, will look :) ty
Tingkai Liu
@TK-21st

Thanks for all the quick replies btw, y'all are awesome!

Question regarding handleComms based on #6929. Suppose the following scenario:

  1. Two instances (widget-1, widget-2) of the same widgets are created (e.g. console), each with a different session pointing to two different kernels
  2. Change one of the widget (widget-1) to use the session of widget-2. This closes all comms that was registered by widget-1 since the new kernelconnection does not handleComms so the registerCommTarget call will be fenced by an if statement.

My question is suppose I want the kernel to talk to the two widgets (now connected to the same kernel) either simultaenously or independently of each other, how would I send data over since widget-2 now has no Comm associated with it?

Or should I force the new KernelConnection associated with widget-1 to handleComms to keep both comms open?
Martha Cryan
@marthacryan
In an extension I'm working on, I use a token provided by another extension (both are external from Jupyterlab). For some reason, the token stopped working after updating our extension to 2.0. Any idea why that might've happened / ideas for debugging? @blink1073
Tingkai Liu
@TK-21st

Hi everyone, I'm running into an issue with extensions that I was hoping someone has a suggestion.
I am running jupyterlab inside a docker container, where I pre-install jupyterlab and all of the extensions as root user. When I run the docker container, I am running as a different user. In this case, the extensions fail to load in jupyterlab because the NPM cache folder is read-only for the current user, with "[...] are not valid NPM packages."
This is actually happening because jupyterlab calls "npm pack" on the extensions, requiring r/w access to the cache. If I chmod the cache first, everything works.
Is there a way to run jupyterlab where this wouldn't be an issue, i.e. it doesn't require r/w access to the original npm cache (that is owned by root on my system)?

@mc-allen have you tried install nodejs within a conda environment? if you have r/w access to the conda/envs dir then you should be fine in that case

Steven Silvester
@blink1073
@marthacryan it may be related to jupyterlab/jupyterlab#7728. I'd check your package.json and run yarn why <foo> in the <app>/staging directory.
Jason Grout
@jasongrout

Or should I force the new KernelConnection associated with widget-1 to handleComms to keep both comms open?

@TK-21st - right now, you'd have to explicitly force the new kernel connection to handle comms. Just be aware that there can be subtle problems with using the same comm from two different clients, where, for example, one client may shut down a comm the other client is using.

The comm protocol very much assumes that it is between a kernel and a single client.