PerilousApricot commented on PR #36176: URL: https://github.com/apache/spark/pull/36176#issuecomment-1274297302
Yes, it's an issue for years now, see https://github.com/jupyterhub/jupyter-server-proxy/issues/57 .. it influences being able to implement functionality like more-functional Jupyter extensions that can query/display the status of jobs inline, and especially since Dask has a very nice JupyterLab extension, it would be good to get this blocker out of the way so that the equivalent can be developed for Spark. Can we at least have the initial https://github.com/apache/spark/pull/31774 PR for 3.3 so *something* works while we wait to get a real solution after all the wait? Then we can code the total fix against the 3.4 branch. > Message ID: ***@***.***> > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
