Hot reloading support in Dash.jl about dash.jl

[waralex]

Hi
What you are now seeing in the master is basically my Dashboards.jl package that provided only basic Dash functionality. Now there is a lot of work on bringing its functionality to the level of Dash in the dev branch.
For example, right now I'm working on the hot reload. But in addition to it, there are many other things that are in Dash that are not yet in Dash.jl. Please be patient, we will definitely bring Dash.jl to the level of other products from the PlotlyDash ecosystem.

[waralex]

@00krishna dev is already very different from master

[00krishna]

Thanks @waralex I totally understand. I am new to even python Dash, so I have a parallel process of pushing my julia code through pyjulia and using python Dash, versus native Julia dash. So that is cool. I will keep playing around with the Julia dash, just to see how it is working. Let me know if I can be of any assistance.

[rpkyle]

Dash for Python's "hot-reloading" feature is described in plotly/dash#66, plotly/dash#362, and plotly/dash-renderer#73.

Supporting this as in the Python and R implementations would require

• creating a hash at app initialization, and regenerating it on file change
• adding a route to serve the hash
• front-end hot reloading (including ability to refresh layout only when CSS updates occur, as well as formatting the JSON response with a modified file manifest)
• back-end hot reloading (reload the app, restart HTTP.jl)
• adding parameters for the dev tools UI: dev_tools_hot_reload, dev_tools_hot_reload_interval, dev_tools_hot_reload_watch_interval, dev_tools_silence_routes_logging
• integration tests for "hard" (restart backend app, reload frontend) and "soft" (CSS only = layout refresh) reloading as in Python and R

On the Python side, we use the Flask debug reloader to reset the hash. We would need to find a comparable approach using HTTP.jl instead.

[00krishna]

@waralex Alexandr, so should the hot-reload feature work now? Seems to indicate that the PR was merged.

[waralex]

@00krishna Yes, it works in dev branch.

[00krishna]

Oh excellent. Nice to know. I can give it a try. If I have any issues, I can always flip back to master branch.

[MLackner]

Maybe this is a stupid question, but how does the hot reloading work practically?
I'm on dev branch and I have my app defined as a module like this:

module MyApp

using Dash
using DashHtmlComponents
using DashCoreComponents

app = dash(external_stylesheets = ["https://codepen.io/chriddyp/pen/bWLwgP.css"])

app.layout = html_div() do
    dcc_input(id = "my-id", value="initial value", type = "text"),
    html_div(id = "my-div")        
end

callback!(app, Output("my-div", "children"), Input("my-id", "value")) do input_value
    "You've entered $(input_value)"
end

end

I tried the following:

(1.3) pkg> activate .
Activating environment at `~/Documents/Julia/MyApp/Project.toml`
julia> using Revise
julia> using MyApp
julia> run_server(MyApp.app, "127.0.0.1", 8080; debug=true)
┌ Warning: Hot reloading is disabled for interactive sessions. Please run your app using julia from the command line to take advantage of this feature.
└ @ Dash ~/.julia/packages/Dash/b6VP7/src/Dash.jl:142
[ Info: Running on http://127.0.0.1:8080

So I put the above code in a file called runserver.jl and from the command line I did

julia --startup-file=no runserver.jl

where I get the following output:

Activating environment at `~/Documents/Julia/MyApp/Project.toml`
Activating environment at `~/Documents/Julia/MyApp/Project.toml`
[ Info: Running on http://127.0.0.1:8080

If I now change the code in my module nothing happens, even if I refresh the page in my browser.
It would be awesome if you guys could give me a hint.

[waralex]

Hi @MLackner
Yes, this may be my mistake - autoreload will not work in this form. Autoreload monitors the executed file and all files included in it (recursively) via include. However, it does not track changes in external packages connected via using or import. If you change runserver.jl, then a restart should occur

[rpkyle]

This feature was added in #25, and is available now in the version released to the Julia Registry. Closing this issue as resolved.