[dev] panic on drop causes process to abort

[skyzh]

As seen in failed CI in #88 , agatedb will abort when we panic on drop. I implemented a partial solution the we ignore all failures (e.g. PoisonedLock, failed to remove file) and simply print them. We could later find a better way to solve this issue.

[skyzh]

Generally, this should not abort, as panic on drop should panic as-is. However, what we may encounter is that, we have panicked, and when rewinding stack to drop, another panic happens. This would cause process abort with no further information.

[skyzh]

SST lost before drop

[skyzh]

This bug is introduced by #87 , where we for the first time enable Agate to be cloned. When an Agate got dropped, all related channels will be closed, and the thread pool will be shutdown. We should wrap Agate with an Arc.

[de-sh]

Is this solved @skyzh?

[skyzh]

Is this solved @skyzh?

Yes. I think I could close this issue for now.