From 04ae25d2c2d7a610439040e665b27b7b9a649ab2 Mon Sep 17 00:00:00 2001 From: Simon Li Date: Mon, 1 Nov 2021 22:14:59 +0000 Subject: [PATCH] use_legacy_stopped_server_status_code: use 1.* language Also fixes the JupyterHub 2.0 default: will be False not True --- jupyterhub/app.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/jupyterhub/app.py b/jupyterhub/app.py index b649f3d5..11ddd7df 100644 --- a/jupyterhub/app.py +++ b/jupyterhub/app.py @@ -1481,8 +1481,8 @@ class JupyterHub(Application): help=""" Return 503 rather than 424 when request comes in for a non-running server. - Prior to JupyterHub 2.0, we returned a 503 when any request came in for - a user server that was currently not running. By default, JupyterHub 2.0 + Prior to JupyterHub 2.0, this returns a 503 when any request comes in for + a user server that is currently not running. By default, JupyterHub 2.0 will return a 424 - this makes operational metric dashboards more useful. JupyterLab < 3.2 expected the 503 to know if the user server is no longer @@ -1490,7 +1490,7 @@ class JupyterHub(Application): true to retain the old behavior, so JupyterLab < 3.2 can continue to show the appropriate UI when the user server is stopped. - This option will default to True in JupyterHub 2.0, and be removed in a + This option will default to False in JupyterHub 2.0, and be removed in a future release. """, config=True,