Yueh-Hsuan Chiang 3aa49e2c69

Keep all erasure coding shreds even on successful recovery (#20968) (#21052) ...

Problem
Blockstore currently removes erasure shreds if the data shreds are
successfully recovered on insert, which is an issue if we want to
serve coding shreds over repair.

Summary of Changes
This diff keeps all coding shreds even on successful recovery and
changes change the signature of prev_inserted_codes to immutable
reference to ensure its immunity.

Fixes #20968

2021-11-16 11:26:34 -08:00

..

benches

Refactor code to get block signatures in get_confirmed_signatures_for_address2 (#20575)

2021-10-13 09:55:19 +02:00

src

Keep all erasure coding shreds even on successful recovery (#20968) (#21052)

2021-11-16 11:26:34 -08:00

tests

removes redundant args from Shredder::try_recovery (#21226)

2021-11-10 21:19:03 +00:00

.gitignore

system_instruction_processor updates (#6448)

2019-10-19 18:23:27 -07:00

build.rs

adds crds-value for broadcasting duplicate shreds through gossip (#14133)

2020-12-18 14:32:43 +00:00

Cargo.toml

chore: bump libc from 0.2.106 to 0.2.107 (#21202)

2021-11-08 12:14:12 -07:00