Oregami
Repositories/oxedyne/fe2o3

fe2o3_mail/tests/imap_move.rs

3 operations, oldest first

created by r1870400018:74938, 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:74938replica 1870400018created fe2o3_mail/tests/imap_move.rs26 days ago under "fe2o3_mail maildir: a failed COPY takes back the copies it filed, and a folder read sweeps stale tmp/ files -- when one message of a COPY could not be copied (an unreadable source; ENOSPC in life), the copies already filed were numbered and kept and the server said try again, so a client that did filed them twice, against RFC 3501 §6.4.7; now they are removed under the target's lock, the removal fsynced, before the folder is read and any is numbered, and MailStore::copy's contract says all or nothing; read_folder removes tmp/ files created over 36 hours ago (the Maildir convention), the writes a crash cut short, by creation time rather than mtime, which write_tmp sets to the INTERNALDATE of an APPEND still in progress outside the lock (F2b part 3, D-20261026-01, QA F2b-A defect 2 and minor; red: imap_move a_failed_copy_leaves_the_target_as_it_was, Archive kept {1: \"f0\"}; green: imap_move 9 / 0, a_folder_read_keeps_a_tmp_file_with_an_old_mtime guards the APPEND case; the sweep of a file over 36 hours old has no failing-first test, as no test can backdate a creation time)"
+r1870400018:74939replica 1870400018inserted 19.6 KiB26 days ago under "fe2o3_mail maildir: a failed COPY takes back the copies it filed, and a folder read sweeps stale tmp/ files -- when one message of a COPY could not be copied (an unreadable source; ENOSPC in life), the copies already filed were numbered and kept and the server said try again, so a client that did filed them twice, against RFC 3501 §6.4.7; now they are removed under the target's lock, the removal fsynced, before the folder is read and any is numbered, and MailStore::copy's contract says all or nothing; read_folder removes tmp/ files created over 36 hours ago (the Maildir convention), the writes a crash cut short, by creation time rather than mtime, which write_tmp sets to the INTERNALDATE of an APPEND still in progress outside the lock (F2b part 3, D-20261026-01, QA F2b-A defect 2 and minor; red: imap_move a_failed_copy_leaves_the_target_as_it_was, Archive kept {1: \"f0\"}; green: imap_move 9 / 0, a_folder_read_keeps_a_tmp_file_with_an_old_mtime guards the APPEND case; the sweep of a file over 36 hours old has no failing-first test, as no test can backdate a creation time)"
+r1870400018:76412replica 1870400018inserted 307 bytes19 days ago under a mark the tool wrote