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
It occasionally happens that a server is running outside of a node. In that case, an updated copy of the server cannot be started unless the old one gets shut down. The manager interface to the browser should allow you to kill connections so that you don't have to hunt them down manually
Fix#247. Implements a close button for each connection on the Manager screen that will kill that connection.
Allows for the killing of servers that have detached from nodes without having to hunt them down manually.
Review: @maffoo and @ejeffrey
It occasionally happens that a server is running outside of a node. In that case, an updated copy of the server cannot be started unless the old one gets shut down. The manager interface to the browser should allow you to kill connections so that you don't have to hunt them down manually
See labrad/scalabrad#62
The text was updated successfully, but these errors were encountered: