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

Increase timeout for the default proxying mechanism #403

Open
banesullivan opened this issue Apr 24, 2023 · 2 comments
Open

Increase timeout for the default proxying mechanism #403

banesullivan opened this issue Apr 24, 2023 · 2 comments

Comments

@banesullivan
Copy link

Proposed change

When launching your own process, you can specify the timeout: https://jupyter-server-proxy.readthedocs.io/en/latest/server-process.html#timeout

This defaults to 5 seconds and (I think) this is the default for the main proxying process too. I'm wondering if we can increase the timeout (or disable it) for the main proxying process provided by jupyter-server-proxy -- the process that is running and accessible under /proxy/<port> as soon as jupyter-server-proxy is installed.

Who would use this feature?

This is needed for the PyVista use case described in #402 where some of our users send large datasets between client/server and the 5 second request timeout causes the whole application to fail.

See pyvista/pyvista#3979 for more details

(Optional): Suggest a solution

Could there be an environment variable to set the default timeout for the main jupyter-server-proxy process we are using in the use cases defined by #402?

@manics
Copy link
Member

manics commented Apr 24, 2023

Support for aliasing /proxy/<port> was added in #339. Configuring the timeout parameter might be supported for this case, have you tried it?

@banesullivan
Copy link
Author

Thank you for pointing out #339! I will attempt to override/alias this with a higher timeout and will report back here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants