Xuanwo

Hi, @jorgehermo9, that will be greatly appreciated. No one is currently working on this. --- Ideally, our cache layer should enable users to design and implement their own cache algorithms...

I have an idea that our future `CacheLayer` can accept an `Operator` instead. Take `foyer` as an example, we can implement a `foyer` service. And use it like: ```rust let...

> I am currently trying to write this CacheLayer (to be used in some multi-layer caching scenarios, such as memory + redis). I might consider submitting a draft PR later...

> Hi [@Xuanwo](https://github.com/Xuanwo), do you expect me to continue in my foyer implementation PR or should I it hand off to [@MrCroxx](https://github.com/MrCroxx)'s work? > > I mean, if my PR...

> I don't think there is anything on that PR that we can reuse for the service... I think it would be better to start from scratch though, I can't...

> 1. We can introduce a new `ErrorKind::RetryableCommitError` to abstract kinds of catalog errors. Hi, I believe it should not be an extra kind. Instead, we can add a `retryable`...

Hi, `stat` is a `HEAD` request, which doesn't have a body, so we don't have additional information to return here. It's very weird that HEAD can return a `400` response...

Hi, @philipmw, thank you for providing more information on this. It's really helpful. I now believe it's related to the `DEEP_ARCHIVE` storage class, which needs to be restored before it...

> Thanks. The command I am running is `rustic init`, and both buckets are newly created and empty. I don't know what archived objects _rustic_ is trying to stat or...

Thanks a lot for your work! @oowl