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
{{ message }}
Repository navigation
OWEwoksWidgetWithTaskStack: provide API to cancel a task #387
For me this part is mostly done. The TaskFuture is a concurrent.futures.Future, and we now are using futures Executor.
So those can be cancelled if not running already.
Then on ewoks side we provide an API to abort those. At the TaskFuture the API is called abort but at ewoks core side it is calling the Task.cancel API. Which is misleading in the name.
It also let the user the role to define how his task should be aborted. That at the time I am still good in the idea because I think it can vary a lot from one use case to the other. It also let us space to determine 'standard' behavior in the future.
I would be in favor to rename ewokscore task.cancel to task.abort and deprecate it in the next ewoks 6.0 version.
Activity
payno commentedon Jun 5, 2026
This was discussed during the ewoks meeting.
Decision was to go to provide future & associated API.
OWWidgetBase.execute_task() -> OWFutureOWFuture.cancel_or_abort(): boolOWFuture.cancel_or_abort()always returns Falsepayno commentedon Oct 6, 2026
For me this part is mostly done. The
TaskFutureis a concurrent.futures.Future, and we now are using futuresExecutor.So those can be
cancelledif not running already.Then on ewoks side we provide an API to
abortthose. At theTaskFuturethe API is calledabortbut at ewoks core side it is calling theTask.cancelAPI. Which is misleading in the name.It also let the user the role to define how his task should be aborted. That at the time I am still good in the idea because I think it can vary a lot from one use case to the other. It also let us space to determine 'standard' behavior in the future.
I would be in favor to rename ewokscore
task.canceltotask.abortand deprecate it in the nextewoks 6.0version.