Joonas Koivunen 68f15cf967 fix: schedule_compaction_update must only unlink (#5675) ...

#5649 added the concept of dangling layers which #4938 uses but only
partially. I forgot to change `schedule_compaction_update` to not
schedule deletions to uphold the "have a layer, you can read it".

With the now remembered fix, I don't think these checks should ever fail
except for a mistake I already did. These changes might be useful for
protecting future changes, even though the Layer carrying the generation
AND the `schedule_(gc|compaction)_update` require strong arcs.

Rationale for keeping the `#[cfg(feature = "testing")]` is worsening any
leak situation which might come up.

2023-10-27 11:16:01 +01:00

..

benches

walredo: make request_redo() an async fn (#5559)

2023-10-18 11:23:06 +01:00

ctl

fix: replace all std::PathBufs with camino::Utf8PathBuf (#5352)

2023-10-04 17:52:23 +03:00

fixtures

walredo: simple tests and bench updates (#3045)

2023-01-16 18:24:45 +02:00

src

fix: schedule_compaction_update must only unlink (#5675)

2023-10-27 11:16:01 +01:00

Cargo.toml

fix: replace all std::PathBufs with camino::Utf8PathBuf (#5352)

2023-10-04 17:52:23 +03:00