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
await link(b).perform();
await wait(1000);
console.log(signal.aborted);
});
const b = task(async (_, { signal })=>{
await wait(1000);
console.log(signal.aborted);
});
a.perform();
b.cancelAll();
In this situation (provided b is cancelled after it starts and before it completes) a will remain in the isRunning state (but this might be removed by the recent updates to how state is derived) indefinitely and will also get no updates about what actually happened to its own task instance.
We need to think about the best path forward for this. Do we want to throw an error into a when b is cancelled so that the task at least has something to show
The text was updated successfully, but these errors were encountered:
In this situation (provided
b
is cancelled after it starts and before it completes)a
will remain in theisRunning
state (but this might be removed by the recent updates to how state is derived) indefinitely and will also get no updates about what actually happened to its own task instance.We need to think about the best path forward for this. Do we want to throw an error into
a
whenb
is cancelled so that the task at least has something to showThe text was updated successfully, but these errors were encountered: