Reduce baseline 503s in our hub infrastructure #2844
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Brings in jupyterhub/jupyterhub#3639 without bringing in all of master. Should eventually help us clean up the spurious 503s. Ref berkeley-dsep-infra#2693
Brings in jupyterlab/jupyterlab#11205, to support us bringing in jupyterhub/jupyterhub#3636 so we can have cleaner 503 error graphs. Ref berkeley-dsep-infra#2693 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brings in jupyterhub/jupyterhub#3636 so we can
stop producing 503 error codes as a baseline even when nothing is wrong.
Bump up JupyterLab to bring in the appropriate PR (jupyterlab/jupyterlab#11205)
from there as well.
Doesn't actually turn the setting on yet.
Ref #2693