https://www.orchest.io/ logo
Powered by
m

Médéric Descazeaux

02/12/2021, 11:05 AM
Hello all, Thank you for the recent updates! After upgrading from 0.6.4 to 0.8.0 (yup, I got distracted), I am getting an error when switching to JupyterLab:
Copy code
Error attempting to connect to Gateway server url '<http://jupyter-EG-someid:8888>'.  Ensure gateway url is valid and the Gateway instance is running.
I can run the scripts from the pipeline view, and I have successfully tried 
curl <http://jupyter-EG-someid:8888>
from orchest-api container to check connectivity. Do you have pointers to help me out?
j

Jacopo

02/12/2021, 11:13 AM
Hi Médéric, Thanks for getting in touch, I'll start looking into this. Is this happening across all pipelines and projects?
m

Médéric Descazeaux

02/12/2021, 11:16 AM
I have only one pipeline and project. 😇
j

Jacopo

02/12/2021, 11:17 AM
Could you try importing the quickstart project (Projects -> import button) and trying to use JupyterLab?
Moreover, if you could run 
./orchest version --ext
and 
./orchest status
that would be very helpful
m

Médéric Descazeaux

02/12/2021, 11:22 AM
I got no issue with the newly imported 
quickstart
project. There you go!
Copy code
➜  orchest ./orchest version --ext
Getting versions of all containers...
orchest/jupyter-enterprise-gateway:latest   : v0.8.0
orchest/jupyter-server:latest               : v0.8.0
orchest/memory-server:latest                : v0.8.0
orchest/orchest-ctl:latest                  : v0.8.0
orchest/update-server:latest                : v0.8.0
orchest/orchest-api:latest                  : v0.8.0
orchest/orchest-webserver:latest            : v0.8.0
orchest/celery-worker:latest                : v0.8.0
orchest/auth-server:latest                  : v0.8.0
orchest/file-manager:latest                 : v0.8.0
orchest/nginx-proxy:latest                  : v0.8.0
orchest/base-kernel-py:latest               : v0.8.0
orchest/base-kernel-py-gpu:latest           : v0.8.0
orchest/base-kernel-r:latest                : v0.8.0
orchest/base-kernel-julia:latest            : v0.8.0
➜  orchest ./orchest status
Orchest is running.
j

Jacopo

02/12/2021, 11:27 AM
Thanks a lot. Happy to hear that a fresh project is working. I am trying to understand what could have gone wrong in your project. You said you were coming from 0.6.4, did you mean 0.6.1 ?
Moreover, could you try: stopping the session, rebuilding the environments that are used in your project/pipeline, then starting the session again?
✅ 1
By the way, I went from 0.6.1 to 0.8.0 and I am able to reproduce the issue
m

Médéric Descazeaux

02/12/2021, 11:47 AM
I made a typo, indeed, it was most likely 0.6.1. Stopping, rebuilding the environment, and starting again the session fixes the issue, thanks!
🎉 2
j

Jacopo

02/12/2021, 11:49 AM
Happy to hear everything went well. I think the issue is related to some outdated kernel specs which have been persisted and haven't been invalidated on update. Will make sure this is taken care of in the next release. Thanks for getting in touch and for using Orchest 🙂
💯 1
🙌 1
r

Rick Lamers

02/12/2021, 12:10 PM
We've quickly discussed - and a fix for this will be on master soon too. So thanks for reporting!
Powered by