Oregami
Repositories/oxedyne/fe2o3

fe2o3_text/src/mime.rs

20 operations, oldest first

created by r1870400018:74762, 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:74762replica 1870400018created fe2o3_text/src/mime.rs26 days ago under "fe2o3_mail maildir: document the one-shot UIDVALIDITY bump -- removing a folder's dovecot-uidlist with Steel stopped is answered by a larger UIDVALIDITY, one marker and UIDs from 1 in delivery order, which the deploy uses to clear any past old-code renumbering (QA-A Info, owner option); the module doc names it and the test that holds it (F2a part 3 fix 3, D-20261026-01)"
+r1870400018:74763replica 1870400018inserted 5.5 KiB26 days ago under "fe2o3_mail maildir: document the one-shot UIDVALIDITY bump -- removing a folder's dovecot-uidlist with Steel stopped is answered by a larger UIDVALIDITY, one marker and UIDs from 1 in delivery order, which the deploy uses to clear any past old-code renumbering (QA-A Info, owner option); the module doc names it and the test that holds it (F2a part 3 fix 3, D-20261026-01)"
+r1870400018:75179replica 1870400018replaced 19 bytes with 12 bytes26 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:75180replica 1870400018inserted 103 bytes26 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:75181replica 1870400018replaced 146 bytes with 419 bytes26 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:75182replica 1870400018replaced 47 bytes with 156 bytes26 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:75183replica 1870400018replaced 8 bytes with 31 bytes26 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:75184replica 1870400018replaced 5 bytes with 3 bytes26 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:75185replica 1870400018replaced 8 bytes with 31 bytes26 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:75186replica 1870400018inserted 24 bytes26 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:75187replica 1870400018replaced 38 bytes with 90 bytes26 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:75189replica 1870400018inserted 19.8 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:75620replica 1870400018inserted 591 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"
+r1870400018:75621replica 1870400018inserted 7 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"
+r1870400018:75622replica 1870400018replaced 57 bytes with 431 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"
+r1870400018:75623replica 1870400018replaced 229 bytes with 498 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"
+r1870400018:75624replica 1870400018replaced 21 bytes with 5 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"
+r1870400018:75625replica 1870400018inserted 6 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"
+r1870400018:75626replica 1870400018inserted 6 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"
+r1870400018:75627replica 1870400018replaced 11 bytes with 262 bytes25 days ago under "Merge origin/main (nohc P1) into mail/f3: one CA bundle list, from TrustConfig"