Hello, I search a bit here and on the web and found out that obviously there is no “official” way to terminate a started task in julia yet. However, throw an Interruption error seems to work as a workaround for now. But now I would like to do it from within a function. Here is the example. The st…

Remove the quoting after @eval, (the :( ... ) part). Right now you just evaluate a value which is an expression: julia> b = @eval :(Base.throwto(t, InterruptException())) :(Base.throwto(t, InterruptException()))

Ups, sometimes it is the easiest stuff which one oversees. After several hours of trying different solutions for my task I finally made a trivial mistake :wink: Thanks…

EDIT: the answer was to use @async for the throwto. One more thing here, when I try to call the function through a toggle in a Blink window, the turning on works but turning off does not. It freezes and the REPL becomes irresponsible. Here is the code using Blink using Interact const run_toggle …

Yes, that might work sometimes, but you’re messing with the internal state of the scheduler, so it’s not really safe. But you’re just controlling the wrong object: sleep is just a thin wrapper around Timer and the Timer object does support start and stop (actually it maybe just exports the new and c…

In this case using start and stop would be great, thanks… However, I would also like to have a possibility to stop a general task without throwing an InterruptExeption which looks a bit awkward to me here.

No, there’s no generally safe way to interrupt a task. But you can interrupt any waitable object (by closing it).

Unlike Base.throwto, schedule is a public API. If it is not safe to use, could you document this? From its docstring, I think it’s impossible for users (like me) to know that it’s an unsafe API: https://docs.julialang.org/en/latest/base/parallel/#Base.schedule

That’s true, it lacks a mention that only the owning queue responsible for managing that task should call that method (and calling that method transfers ownership to a new queue)

Thanks. Does it mean that, as a user, it is valid to call schedule(t, exception, error=true) only if the task is not scheduled yet, like this? julia> t = @task nothing Task (runnable) @0x00007f3b6dd9cc40 julia> schedule(t, InterruptException(), error=true) Task (failed) @0x00007f3b6dd9cc40 Interr…

Right, if you just made the task, that’s an example of when you own it. You also usually own current_task() (which is good, because wait and yield etc. will implicitly take ownership of it), so you can also de-schedule yourself (e.g. call wait()), or throw exceptions (schedule(error=true); wait(), o…

Stop/terminate a (sub)task started with @async

General Usage

tkf December 15, 2019, 3:47am 6

Is using schedule(t, InterruptException(), error=true) instead of @async Base.throwto(t, InterruptException()) correct here?

Topic		Replies	Views
How to interrupt async tasks? General Usage	7	2074	March 27, 2022
Task termination New to Julia task , async	7	2110	December 9, 2024
How to stop a task started with `@schedule` New to Julia	1	1292	December 8, 2017
How to interrupt fun(a,b) in a for loop after 10 seconds? General Usage	27	1043	April 17, 2024
Interrupts in @async code General Usage task , async , interruptexception	20	1259	July 19, 2023

Stop/terminate a (sub)task started with @async

Related topics