Arpad Müller

For context: I'm doing a setup where rust-cross-libs is its own buildroot package, and rust src and rust binaries are two host packages; both obtained from tarballs of that form.

> Why not use `--rust-git`? Buildroot has this property that the source code for all packages it downloads is downloaded ahead of the actual build steps, and put inside the...

This is really great work, amazing!

I added the test in #5390 as a copy of `test_wal_restore` mostly. I wonder, is `test_wal_restore` also flaky due to https://github.com/neondatabase/neon/pull/5948?

I've replied on [slack](https://neondb.slack.com/archives/C033RQ5SPDH/p1703185206226579) already, but putting it here as well. This is expected behaviour. `initdb.tar.zst` is useful as long as WAL exists on S3, because as long as WAL...

Thinking about the entire "what to do with initdb deletion and the recovery scenario" more, I think that the best solution is to: * have deletion delete `initdb.tar.zst` unconditionally *...

first CI failure [debug](https://github.com/neondatabase/neon/actions/runs/7261233707/job/19782039107): ``` thread 's3_time_travel_recovery_works' panicked at libs/remote_storage/tests/test_real_s3.rs:215:5: assertion `left == right` failed left: {RemotePath("test/path1"), RemotePath("test/path2")} right: {RemotePath("test/path2"), RemotePath("test/path3")} ``` release: ``` thread 's3_time_travel_recovery_works' panicked at libs/remote_storage/tests/test_real_s3.rs:215:5: assertion...

I made it work locally, it still errors when I run it in the CI...

> especially for layer files, where they are totally inert if not referenced by an index: in DR there is no utility to deleting these, it is alway sufficient to...

I have now implemented the new approach outlined in https://github.com/neondatabase/cloud/issues/8233#issuecomment-1858540063 and the unit test is green. I will remove some debug prints next, but reviews are welcome.