You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lt's relatively easy (e.g. #3799) to introduce memory leaks in application reloading. Or have misbeaving application run out of other resources (run out of file descriptors, sockets) or have globalness (loading a native library, setting a system property, registering URL handlers).
The classloader reload is superior for speed, but it would be nice to have the choice to stop and restart an process, for robustness.
There was sbt-fork-run-plugin but it hasn't worked for some time, and was recently removed altogeher.
The text was updated successfully, but these errors were encountered:
The idea I have for dev mode is to have some sort of thin proxy server that holds the HTTP/HTTPS ports open and then forwards traffic to the user's application. The proxy server forwards traffic if the application compiles OK or shows an error message otherwise. However, this is quite a lot of work…
lt's relatively easy (e.g. #3799) to introduce memory leaks in application reloading. Or have misbeaving application run out of other resources (run out of file descriptors, sockets) or have globalness (loading a native library, setting a system property, registering URL handlers).
The classloader reload is superior for speed, but it would be nice to have the choice to stop and restart an process, for robustness.
There was sbt-fork-run-plugin but it hasn't worked for some time, and was recently removed altogeher.
The text was updated successfully, but these errors were encountered: