Oregami
Repositories/oxedyne/fe2o3

fe2o3_o3db_sync/src/textscan.rs

6 operations, oldest first

created by r1870400018:67327, 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:67327replica 1870400018created fe2o3_o3db_sync/src/textscan.rs46 days ago under "fe2o3_o3db_sync gateway: open_store gives the answer count, require_answer refuses 0, and the scanner says where (U0-15)"
+r1870400018:67328replica 1870400018inserted 4.4 KiB46 days ago under "fe2o3_o3db_sync gateway: open_store gives the answer count, require_answer refuses 0, and the scanner says where (U0-15)"
+r1870400018:69920replica 1870400018replaced 120 bytes with 159 bytes42 days ago under "fe2o3_o3db_sync verify: a read-only check of every live value, which names each torn chunked value by its key, and an open that is only read from now writes nothing"
+r1870400018:69921replica 1870400018inserted 17 bytes42 days ago under "fe2o3_o3db_sync verify: a read-only check of every live value, which names each torn chunked value by its key, and an open that is only read from now writes nothing"
+r1870400018:69922replica 1870400018replaced 52 bytes with 48 bytes42 days ago under "fe2o3_o3db_sync verify: a read-only check of every live value, which names each torn chunked value by its key, and an open that is only read from now writes nothing"
+r1870400018:73839replica 1870400018replaced 45 bytes with 68 bytes40 days ago under "fe2o3_o3db_sync: a scan lists the keys with a live value and leaves deleted keys out (Ozone scan leaves deleted keys out) -- the scan bot walks the index files, which name each key's newest record but not its value, and emitted every kept key, so a key whose newest record is a tombstone was listed while every read of it came back empty (the Daimond gateway's G2b session migration miscounted on it), and every retired chunk key leaked into the main-key scan the same way. ScanBot::drop_deleted reads, after the newest-wins dedup, each Complete record whose value has the tombstone's length (one writer, one unencrypted form), confirms it is the record the index named (key, stamp, checksum), and drops it when its value is the deleted kind; each data file is opened before its index is walked, and a record that is not the one named (a collection between the two opens) repeats the pass, then fails loud. Sweep, verify, textscan, migrate, cas and dist digests treated an absent read as skip and need no tombstones; cas_o3db::ids drops its per-key read. Contract documented on OzoneApi::scan and Database::scan. tests/scan_after_delete.rs 2/2 (live, restart, index replay, compact_now, compact and restart; red on origin/main with 8 deleted and 64 chunk keys listed; mutant without the filter red); verify and migrate tests moved to the new contract. Full crate 222/223, the one failure a load-timed footprint assertion that calls no scan and passes alone; --features dist 423/423; cargo build --workspace clean."