I agree with the display() change, though it might be simpler to just allow host to include the scheme and parse it out if provided. Parameters have default values taken from module globals set by a newįunction. The simpler %tensorboard magic interface, we could let these Kwargs host and protocol that control the origin of the iframe,ĭefaulting to 'localhost' and 'http', respectively. If we wanted to add support for this, my initial thoughts would be asįollows. The information through the TensorBoard info file, but I don’t think
Right thing to do if you wanted to add a new flag would be to thread The underlying tensorboard(1) binary actually parses them. Provided by the user are merely lexed by the notebook extension only TensorBoard in the UI is not actually an easy patch: the arguments (Namely: it has different semantics from what you seem to want.)įurthermore, reading an argument value to determine how to render TensorBoard already accepts a -host command-line argument, whichĬontrols the interfaces to which the server will attempt to bind. Worker proxy forwards requests to to the actual Was to have solid support for TensorBoard in Colab-in Colab, a service We discussed this as part of the originalĭesign, and didn’t assign it a high priority because the initial goal
