Oregami
Repositories/oxedyne/fe2o3

fe2o3_o3db_sync/tests/qa2_reclaim.rs

14 operations, oldest first

created by r1870400018:70213, 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:70213replica 1870400018created fe2o3_o3db_sync/tests/qa2_reclaim.rs42 days ago under "fe2o3_o3db_sync: a stamp floor and one tie order -- a write after a restart outranks every record on disk even after the clock steps back, and two records of a key with one stamp are ordered by place in every path, so a key reads the same value live and after a restart (Ozone run 1) Replay raises the process's stamp clock past every stamp it reads (api::raise_stamp_floor in both bot_initgc replay paths) before start returns, and every record, tombstones included, is stamped through api::write_stamp (pending.rs own-set retire, data/core.rs zero-time record); KeyVal::stamp_time_now is gone. data::cache::supersedes orders by (time, fnum, offset) and is shared by Cache::insert, replay and bot_scan."
+r1870400018:70214replica 1870400018inserted 15.7 KiB42 days ago under "fe2o3_o3db_sync: a stamp floor and one tie order -- a write after a restart outranks every record on disk even after the clock steps back, and two records of a key with one stamp are ordered by place in every path, so a key reads the same value live and after a restart (Ozone run 1) Replay raises the process's stamp clock past every stamp it reads (api::raise_stamp_floor in both bot_initgc replay paths) before start returns, and every record, tombstones included, is stamped through api::write_stamp (pending.rs own-set retire, data/core.rs zero-time record); KeyVal::stamp_time_now is gone. data::cache::supersedes orders by (time, fnum, offset) and is shared by Cache::insert, replay and bot_scan."
+r1870400018:71196replica 1870400018replaced 49 bytes with 12 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71197replica 1870400018replaced 1 byte with 1 byte40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71198replica 1870400018replaced 61 bytes with 3 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71203replica 1870400018inserted 188 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71204replica 1870400018inserted 1.7 KiB40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71206replica 1870400018replaced 4 bytes with 91 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71207replica 1870400018inserted 44 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71208replica 1870400018inserted 3 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71209replica 1870400018inserted 5 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71210replica 1870400018inserted 107 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71211replica 1870400018inserted 3 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"
+r1870400018:71212replica 1870400018inserted 5 bytes40 days ago under "fe2o3_o3db_sync: a failed cut back whose fault record cannot be written is held by the refusal marker alone, which carries its cut, and clearing the marker folds the cut into the record so the next open cuts the pair back -- a test now pins that path of the round-2 marker; and the torn-append error no longer carries a run of spaces from a string continued without its backslash (Ozone APPENDSEEK, rebase onto round 2)"