This commit introduces a new alias `custom_display_url` to override the
URL info displayed at launch with a custom string.
It is intended to be used when the app is run in an environment where
the url to display to the users is not detectable reliably (proxified or
containerized setups for example).
Noticed in test output that creating HMAC without digestmod arg is deprecated.
While there, use proper length of 32 bytes for default tornado cookie_secret. There’s no benefit to using a cookie secret that's longer that the cookie digest size, which is 32 bytes.
* Add support for terminals on Windows
* Bump terminado requirement
* Fix handling of default shell
* Fix appveyor syntax
* Fix requires syntax
* Fix version target
* Clean up handling of default shell and update version check
* Always require terminado
* Clean up appveyor test
* Make the terminado warning uniform
* Default to powershell on Windows
* Clean up terminado verison
Currently changing the password does not revoke current session:
- jupyter notebook password <password1>
- jupyter notebook
- Logging in
- Kill server
- jupyter notebook password <other password>
- jupyter notebook
- Oh ! I'm still logged in.
With this, as the "effective" secret depends on the (hashed) password,
changing it void any existing session (which I believe is the goal of
most password change)
Signals don't work on Windows. This tries the HTTP shutdown request first.
On Unix, it will try SIGTERM after 5 seconds, and SIGKILL after another 5, if the
server didn't already exit.
Closes gh-2937
loop.stop() will not be safe from a thread in tornado 5
There has never been a guarantee to this effect,
but it has happened to be true so far.
The result is that the stop event will not fire until the next loop iteration (e.g. triggered by an HTTP request).
Using add_callback ensures that the main thread wakes and handles the stop event.
cf tornado#2119