This repository has been archived by the owner on Nov 8, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 294
Unloading a plugin should kill instances of the plugin that are running #1061
Comments
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 21, 2016
… are stopped/killed on unload
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 22, 2016
… are stopped/killed on unload
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 22, 2016
… are stopped/killed on unload
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 22, 2016
… are stopped/killed on unload
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 22, 2016
… are stopped/killed on unload
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 22, 2016
… are stopped/killed on unload
IRCody
added a commit
that referenced
this issue
Jul 25, 2016
Fixes #1061: ensures that all instances of a running plugin are stopped
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Given you start the example mock-file.yaml task and then unload the mock plugins the latest plugin, which was the one running, will still be running after unloading it.
The text was updated successfully, but these errors were encountered: