-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jupyter lab build ==4.2.0 unable to get issuer certificate #16316
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
|
1 - after installing for exemple some labextension such as the scheduler..... you may think it's related with those labextensions but not , even having only jupyterlab installed on the virtual env i could not run jupyter lab build so it's probably not related with labextension. 2- jupyter lab build thank you so much for your quick reply . |
|
we use jupyterlab-scheduler which is cron based. i'm trying to upgrade jupyterlab from 3.6.4 to 4.2.0 which means soof the extension are already installed with jupyter labextension install. so even jupyter server extension enable --user --py jupyter_scheduler does not resolve my issue is there any cron scheduler similar to jupyterlab-scheduler ? thanks |
difference between https://github.com/jupyter-server/jupyter-scheduler, and https://pypi.org/project/jupyterlab-scheduler/ is that jupyter-scheduler depends on your jupyterlab session it does not run in the background , but jupyterlab-scheduler does uisng papermill or nbconvert , so even if a user end or logout from his session his jobs/notebooks will run as expected . that's why I'm looking for anything similar to it ? |
It is not clear to me if the extension you are trying to use even works with JupyterLab 4.x as per tiburon-security/jupyterlab_scheduler#25
https://github.com/nebari-dev/argo-jupyter-scheduler that I mentioned can run tasks in the background the same way as cron would, but it has a dependency on argo, conda-store (for environment management) and I do not think it was tested outside of nebari so it may or may not be good fit for you -depending on what your deployment is. |
so now the question is: thanks |
As I mentioned in tiburon-security/jupyterlab_scheduler#25 (comment), you can run Jupyter notebooks unattended, on a schedule, without having JupyterLab running, by using Note that "JupyterLab Scheduler" is a separate project than "Jupyter Scheduler"; the latter is officially maintained as part of the Jupyter Server organization, whereas the former is maintained by a third party. The latter's 1.x release will remain in maintenance until JupyterLab 3.x's nominal end of maintenance date, which is 2024-05-15 (tomorrow). We can keep the conversation going in the |
i'm not able to rebuild jupyterlab.
os : redhat
node : v20.11.1
npm : 10.7.0
YN0001: │ RequestError: unable to get issuer certificate
at ClientRequest. (/openprog/VirtualPython/lib/python3.11/site-packages/jupyterlab/staging/yarn.js:195:14340)
at Object.onceWrapper (node:events:633:26)
at ClientRequest.emit (node:events:530:35)
at o.emit (/openprog/VirtualPython/lib/python3.11/site-packages/jupyterlab/staging/yarn.js:190:90286)
at TLSSocket.socketErrorListener (node:_http_client:495:9)
at TLSSocket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
at TLSSocket.onConnectSecure (node:_tls_wrap:1674:34)
at TLSSocket.emit (node:events:518:28)
at TLSSocket._finishInit (node:_tls_wrap:1085:8)
at ssl.onhandshakedone (node:_tls_wrap:871:12)
The text was updated successfully, but these errors were encountered: