-
Notifications
You must be signed in to change notification settings - Fork 5
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
Cell timeout (presumably due to the large output) #157
Comments
@volodymyrss @burnout87 seems we will need a file storage for this also |
did you try this? |
I don't really see how it's related. Our case rather corresponds to what is discussed in nteract/papermill#426 The event file here is ~35M, apart from the abovementioned buffer problem, this is already quite a lot to send it in an http response. |
How to reproduceThe above error was caused by karabo-dirty-image-sim workflow. To reproduce use the parameters: Working caseThe workflow works if you set Additional infoThe timeout happens in the function |
could @anawas check what is the size of the output? Maybe it hits a problem and we need to adjust something. |
Running model_CTA_events_from_file with default parameters in MMODA leads to the backend exception
which refers to the injected cell where outputs are glued.
This affects the overall user experience, in the frontend I first get gateway timeout. Also, this problem seems to somehow interact with the callback, if I re-request just after the timeout, the status is constantly "progress". Subsequent re-request shows the actual backend exception.
I didn't manage to reproduce the issue by running nb2workflow locally (with the fresh environment installed from requirements.txt). But it's reproducible by running the container in the local docker.
The text was updated successfully, but these errors were encountered: