-
Notifications
You must be signed in to change notification settings - Fork 354
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
Visual feedback that the hub restarted #112
Comments
I think I was partially (and unconsciously) following the ol' school unix setup of 'if everything went ok, output nothing'. I think that's the wrong thing here, so we should fix that. JSON Schema validation! <3 |
I think "output nothing on success" would work if we tell the user that 100% guaranteed there will be a message you can not miss if something went wrong. In my case I had a typo in the config, got no feedback from restarting, and did not observe my attempted reconfiguration taking effect. Which made me wonder "config wrong or mistake restarting or need to restart more??" |
I created an issue for implementing JSONSchema validation of our config as it is a relevant separate task in #725. Is it correct that this regards I think to indicate success, is the same as to ensure we have no errors. So in my mind, the gist of this issue is to validate the outcome of the The current tljh-config reload logic is defined here. the-littlest-jupyterhub/tljh/config.py Lines 257 to 279 in 26811a8
Aha! It seems like this is already resolved. I'll go for a close on this issue! |
Right now when restarting the hub there is almost now feedback on whether that worked or not. In particular if you are running the restart command from a web terminal in your single-user server.
Having some kind of feedback that "jupp this thing restarted and loaded your newly modified configuration" would be good. Mostly as a way to reassure users. Even better would be if there was some validation of the configuration before restarting and a corresponding error message. In particular checking for yaml keys that aren't recognised as they are potential typos.
The text was updated successfully, but these errors were encountered: