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
"lt3 dev" server sometimes crashes on OSX with node 0.8.x on an Abort 6 error. Updating to 0.10.x may prevent some of that as there have been updates to watch for errors like this in some core libraries. The main issue is that the server should restart in the case of a crash like this.
Let's research/discuss the best way to handle this.
one option is to use the built-in cluster to listen for failure and spawn a new process. I haven't tested cluster out on windows, so not sure if we'd run into issues there.
Another point of discussion would be how to re-auth the user after a crash. Right now authentication happens when connecting in the browser, maybe we should consider using the local auth token stored in .lt3_config on server startup.
The text was updated successfully, but these errors were encountered:
"lt3 dev" server sometimes crashes on OSX with node 0.8.x on an Abort 6 error. Updating to 0.10.x may prevent some of that as there have been updates to watch for errors like this in some core libraries. The main issue is that the server should restart in the case of a crash like this.
Let's research/discuss the best way to handle this.
one option is to use the built-in cluster to listen for failure and spawn a new process. I haven't tested cluster out on windows, so not sure if we'd run into issues there.
Another point of discussion would be how to re-auth the user after a crash. Right now authentication happens when connecting in the browser, maybe we should consider using the local auth token stored in .lt3_config on server startup.
The text was updated successfully, but these errors were encountered: