Arpad Müller

It has fulfilled its purpose, we can close this now, right?

closing as I haven't heard a "no" response.

With https://github.com/neondatabase/neon/pull/6821 it is more complex now: we have to both implement waiting on the child pageserver and also think about not blocking the request on the parent attachment_service server

If the HTTP response times out, it doesn't continue in the background. If within the timeout period, the recovery gets to the phase where it's not doing list calls but...

Recently it started to re-occur again:  edit: #7201

Closing as https://github.com/neondatabase/neon/pull/6830 has been merged.

I cannot reproduce it either

One can make a custom tuple struct `#[must_use] pub struct BufWithResult(pub B, pub Result)`.

Apparently the CI tests hit https://github.com/neondatabase/tokio-epoll-uring/issues/46 . I asked Christian about it who suggested me to change the API to take a slice. So I wrote https://github.com/neondatabase/neon/pull/8225 .

This week: * https://github.com/neondatabase/neon/issues/8459 * https://github.com/neondatabase/neon/issues/8460