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
If I run a long (and possibly buggy) simulation from the repl, I can't really kill it without restarting the repl entirely.
I think ideally sending a cider-interrupt or equivalent should kill the whole thing, which I guess doesn't work out of the box because it's using heavily core.async under the hood right?
The text was updated successfully, but these errors were encountered:
I have used the exit channel mechanism (a.k.a. poison pill) in other projects using core.async. This kind of feature could be added to clj-gatling too. For example there could be a function kill-all-running-simulations which would send message to all exit channels.
If I run a long (and possibly buggy) simulation from the repl, I can't really kill it without restarting the repl entirely.
I think ideally sending a cider-interrupt or equivalent should kill the whole thing, which I guess doesn't work out of the box because it's using heavily core.async under the hood right?
The text was updated successfully, but these errors were encountered: