Oregami
Repositories/oxedyne/fe2o3

fe2o3_o3db_sync/tests/lane.rs

2 operations, oldest first

created by r1870400018:74447, which is this file's identity for as long as the history lasts, whatever it is later renamed to

read the file · who wrote it · compare two states

An operation carries no clock of its own. Each row is therefore dated by the first mark written after it by the same replica, which is one copy of the repository, and that mark is where the command that wrote the operation ended.

+ signed and verified, ? signed by a key this forge does not carry, - unsigned

OperationAuthorWhatWhen
+r1870400018:74447replica 1870400018created fe2o3_o3db_sync/tests/lane.rs33 days ago under "fe2o3_o3db_sync: a due period barrier is never starved by a long put's chunks; R1 test made sensitive (Ozone chunk barriers, QA B A1 A3) -- under Interval a plain record that lands with the period not due is covered by the syncer's timer alone, and a syncer lagging its writer through a long put always found a chunk waiting, so the timer never ran out and the record waited for the put's own SyncNow (A1). Syncer::run now checks owed_in() after each item it takes in, not after each batch, since one batch can be a long put's every chunk; the old held-discard check is folded into it. New hook test::hooks::set_syncer_chunk_delay; new tests/chunk_period.rs cuts 800 ms after a plain record's ack while a 1,500-chunk put holds a lagging syncer: red on 4e5869b5 (record lost), green after; removing the new check reddens it again. A3: chunk_barriers asserts each barriered writer is in a distinct zone and gains chunk_phase_every_n; head_hold's comment says it covers one put at a time. QA A F-1/F-2: durable_mark::a_head_never_outlives_its_chunks rebuilt with 1 MiB data files, a 900 ms barrier delay and a cut at the head hold, over every policy at 1x1, 1x4 and 2x2, counting exactly the one store's new chunk keys: under M8 (chunk answers unheld) it fails 9/9 non-EveryWrite cases (8 of 8 chunks missing), green on the real code. Targeted gate 41/41 (chunk_barriers 6, chunk_hold 6, chunk_period 1, durable_mark 14, durable_mark_races 4, lone_index 10); full package, --features dist and the workspace build not yet run on this commit."
+r1870400018:74448replica 1870400018inserted 26.2 KiB33 days ago under "fe2o3_o3db_sync: a due period barrier is never starved by a long put's chunks; R1 test made sensitive (Ozone chunk barriers, QA B A1 A3) -- under Interval a plain record that lands with the period not due is covered by the syncer's timer alone, and a syncer lagging its writer through a long put always found a chunk waiting, so the timer never ran out and the record waited for the put's own SyncNow (A1). Syncer::run now checks owed_in() after each item it takes in, not after each batch, since one batch can be a long put's every chunk; the old held-discard check is folded into it. New hook test::hooks::set_syncer_chunk_delay; new tests/chunk_period.rs cuts 800 ms after a plain record's ack while a 1,500-chunk put holds a lagging syncer: red on 4e5869b5 (record lost), green after; removing the new check reddens it again. A3: chunk_barriers asserts each barriered writer is in a distinct zone and gains chunk_phase_every_n; head_hold's comment says it covers one put at a time. QA A F-1/F-2: durable_mark::a_head_never_outlives_its_chunks rebuilt with 1 MiB data files, a 900 ms barrier delay and a cut at the head hold, over every policy at 1x1, 1x4 and 2x2, counting exactly the one store's new chunk keys: under M8 (chunk answers unheld) it fails 9/9 non-EveryWrite cases (8 of 8 chunks missing), green on the real code. Targeted gate 41/41 (chunk_barriers 6, chunk_hold 6, chunk_period 1, durable_mark 14, durable_mark_races 4, lone_index 10); full package, --features dist and the workspace build not yet run on this commit."