Skip to content
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

Closed
mouatez25 opened this issue May 10, 2024 · 10 comments
Closed

jupyter lab build ==4.2.0 unable to get issuer certificate #16316

mouatez25 opened this issue May 10, 2024 · 10 comments
Labels
bug status:Needs Triage Applied to new issues that need triage

Comments

@mouatez25
Copy link

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)

@mouatez25 mouatez25 added the bug label May 10, 2024
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label May 10, 2024
Copy link

welcome bot commented May 10, 2024

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@krassowski
Copy link
Member

  1. Why are you rebuilding JupyterLab?
  2. How are you rebuilding JupyterLab?
  3. Do you have HTTP(S) proxy setup?

@mouatez25
Copy link
Author

mouatez25 commented May 10, 2024

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
3- we don't

thank you so much for your quick reply .

@krassowski
Copy link
Member

  1. In JupyterLab 3+ you should not need to rebuild JupyterLab after installing an extension and you should not use jupyter labextension install which is deprecated for installing extensions since JupyterLab 4. Instead you should install extensions using pip install or conda install. If you mean https://github.com/jupyter-server/jupyter-scheduler, please note that it lists pip install jupyter_scheduler in installation instructions.

@mouatez25
Copy link
Author

we use jupyterlab-scheduler which is cron based.
https://pypi.org/project/jupyterlab-scheduler/

image

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

image

is there any cron scheduler similar to jupyterlab-scheduler ?

thanks

@mouatez25
Copy link
Author

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 ?

@krassowski
Copy link
Member

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

jupyter-scheduler allows to swap out the scheduling engine which is for example what argo-jupyter-scheduler does so I imagine that you can also swap it for cron a scheduler too.

that's why I'm looking for anything similar to it ?

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.

@mouatez25
Copy link
Author

mouatez25 commented May 13, 2024

thank you for you answers!!

I was able before to change some line of codes( setup.py + package.json)to make it work with jupyterlab 3.6.4,i'm trying to do the same with jupyterlab4 .

even using pip only to install the package does not work and give me the error message mentioned before.

image

@mouatez25
Copy link
Author

so now the question is:
do we have a scheduler which does not depend on jupyerlab session to install in linux ( no argo , no container ...)

thanks

@JasonWeill
Copy link
Contributor

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 crond or another unattended scheduler with a program such as papermill that can run your notebooks independently of JupyterLab or Jupyter Server.

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 jupyterlab_scheduler issue linked above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug status:Needs Triage Applied to new issues that need triage
Projects
None yet
Development

No branches or pull requests

3 participants