Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JupyterLab/Local pipeline execution fails with "Expected token < in JSON ..." for long running tasks
See original GitHub issueDescribe the issue See steps below. I was only able to always reproduce this on ODH, but not locally.
To Reproduce Steps to reproduce the behavior:
- In ODH launch JupyterHub and choose in the spawner dialog the
s2i-lab-elyra:vX.Y.Zimage - Git clone https://github.com/elyra-ai/examples.git
- Open the NOAA pipeline.
- Run the pipeline locally.
There is no error logged in the Jupyter console. The web browser indicates that the POST https://jupyterhub-1-0-9-test.ptitzler-odh-442dbba0442be6c8c50f31ed96b00601-0000.sjc04.containers.appdomain.cloud/user/iam%23ptitzler@us.ibm.com/elyra/pipeline/schedule?1618515969761 request fails with status code 504, returning this message text:
<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>`
which causes the JSON parser error.
Expected behavior A clear and concise description of what you expected to happen.
- The front end should catch processing errors.
- Not sure to what extend the front end can provide a meaningful message since it doesn’t know whether the back-end sent “garbage”, whether the backend timed out and the long running request is still processing.
- Insights why this always happens on ODH/JupyterHub/JupyterLab but not locally. The “long running job” completed within a few minutes and didn’t seem to be taking longer than usual.
Deployment information Describe what you’ve deployed and how:
- Elyra version: 2.2.1
- Installation source: official container image
s2i-lab-elyra:v0.0.7 - Deployment type: Open Data Hub
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
the deployment on openshift doesn’t appear to have any ingresses or routes configured in the odh project/namespace, so it’s probably using some global default. Short term, going to see if a quick config change will do the trick, but agree with
I am seeing this error when I attempt to run in our Kubernetes Z2JH environment. If run the container that has Elyra installed (same thats used in the k8s cluster) it works. I am seeing a 403 error in the browser console at the
elyra/pipeline/schedule?1657211511533endpoint.