Dmitry Rodionov fb68d01449 Preserve task result in TaskHandle by keeping join handle around (#2521) ...

* Preserve task result in TaskHandle by keeping join handle around

The solution is not great, but it should hep to debug staging issue
I tried to do it in a least destructive way. TaskHandle used only in
one place so it is ok to use something less generic unless we want
to extend its usage across the codebase. In its current current form
for its single usage place it looks too abstract

Some problems around this code:
1. Task can drop event sender and continue running
2. Task cannot be joined several times (probably not needed,
    but still, can be surprising)
3. Had to split task event into two types because ahyhow::Error
    does not implement clone. So TaskContinueEvent derives clone
    but usual task evend does not. Clone requirement appears
    because we clone the current value in next_task_event.
    Taking it by reference is complicated.
4. Split between Init and Started is artificial and comes from
    watch::channel requirement to have some initial value.

    To summarize from 3 and 4. It may be a better idea to use
    RWLock or a bounded channel instead

2022-09-26 20:57:02 +00:00

..

src

Preserve task result in TaskHandle by keeping join handle around (#2521)

2022-09-26 20:57:02 +00:00

Cargo.toml

R-Tree layer map (#2317)

2022-09-22 08:35:06 +03:00