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 would be quite useful to have a ExtendedTask$Kill() method that would kill the respective process associated with the task. Such method would better handle cases of expensive tasks where user decides to change inputs half-way. Such actions would create multiple processes running expensive tasks, which is something we want to avoid.
Concept:
ExtendedTask$kill() # kill all previous taskExtendedTask$invoke() #start a new task based on new input
The text was updated successfully, but these errors were encountered:
Based on jcheng5's example solution; I've made a further gist to demonstrate how with R6 subclassing, we can make the $kill() though (I called it $stop_m in my example, for a Mirai backed extendedTask) link
Thanks ExtendedTasks implementation, it has a promissing future!
As of shiny 1.8.1.1, the methods available for ExtendedTasks are:
It would be quite useful to have a
ExtendedTask$Kill()
method that would kill the respective process associated with the task. Such method would better handle cases of expensive tasks where user decides to change inputs half-way. Such actions would create multiple processes running expensive tasks, which is something we want to avoid.Concept:
The text was updated successfully, but these errors were encountered: