Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose "kill client" for manager browser #247

Closed
ejeffrey opened this issue Jul 26, 2016 · 1 comment · Fixed by #248
Closed

Expose "kill client" for manager browser #247

ejeffrey opened this issue Jul 26, 2016 · 1 comment · Fixed by #248
Assignees
Milestone

Comments

@ejeffrey
Copy link

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

@adamcw adamcw added this to the v2.0 milestone Jul 26, 2016
@adamcw
Copy link
Contributor

adamcw commented Jul 26, 2016

From my understanding, this is a feature required for parity so I've marked it v2.0.

@adamcw adamcw self-assigned this Jul 26, 2016
adamcw added a commit that referenced this issue Jul 29, 2016
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
@adamcw adamcw removed the pr-pending label Aug 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants