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

Kill all for Phantom JS processes #666

Closed
acravenho opened this issue Sep 2, 2018 · 0 comments · May be fixed by baophucct/blockscout#4
Closed

Kill all for Phantom JS processes #666

acravenho opened this issue Sep 2, 2018 · 0 comments · May be fixed by baophucct/blockscout#4
Labels
enhancement New feature or request priority: medium Issues with a medium priority severity: 4 Lowest severity. team: architecture
Milestone

Comments

@acravenho
Copy link
Contributor

As talked about during demo, it would be great to have such a feature to kill all Phantom JS processes.

@acravenho acravenho added enhancement New feature or request team: architecture priority: low Low priority issues labels Sep 2, 2018
@acravenho acravenho added this to the Kuala Lumpur milestone Sep 2, 2018
@acravenho acravenho added priority: medium Issues with a medium priority severity: 4 Lowest severity. and removed priority: low Low priority issues labels Sep 10, 2018
@acravenho acravenho moved this from To do to Done in Architecture, Workers, Database Feb 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: medium Issues with a medium priority severity: 4 Lowest severity. team: architecture
Development

Successfully merging a pull request may close this issue.

1 participant