fe2o3_o3db_sync/tests/encrypted_delete.rs
2 operations, oldest first
created by r1870400018:74394, 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
| Operation | Author | What | When | |
|---|---|---|---|---|
| + | r1870400018:74394 | replica 1870400018 | created fe2o3_o3db_sync/tests/encrypted_delete.rs | 35 days ago under "fe2o3_steel alert, watch: a failed alert mail falls back to a text of the alert itself, and a burst of shield drops is not distress until sustained -- ChannelFailing gains missed_text (the lost alert's one-line form), so a mail failure is texted as that alert with \" (mail failing)\" (or \", n lost\") as a suffix, cut to one 160-char SMS part (fit_text, SMS_PART), never a bare \"alert mail FAILING\"; ChannelBook::note takes the event and host; Alerter::owed sends no second text for an alert already texted, and text_of suffixes every text while mail is in a failing run; WatchPeer gains a per-field `sustain` map (consecutive over-threshold readings before a class is distress, in place of fail_threshold), PeerState keeps per-class runs, SUSTAIN_DEFAULTS gives dropped_1m 10, a burst short of it logs \"not yet sustained; no alert\", and reminders name only sustained classes (16 Oct 2026: a scanner's bursts at birch, dropped_1m 215, were told as distress and the owner got only \"[steel:karri] alert mail FAILING (1 in a row)\"; red: test_a_failed_mail_falls_back_to_a_text_of_the_alert_00 got \"karri: alert mail FAILING\", a_drop_burst_is_not_distress_until_it_is_sustained fired at round 2; green: steel lib 340, with test_a_texted_alert_is_not_texted_again_when_its_mail_fails_00 and the stuck-mail-leg test now asserting one text)" |
| + | r1870400018:74395 | replica 1870400018 | inserted 8.0 KiB | 35 days ago under "fe2o3_steel alert, watch: a failed alert mail falls back to a text of the alert itself, and a burst of shield drops is not distress until sustained -- ChannelFailing gains missed_text (the lost alert's one-line form), so a mail failure is texted as that alert with \" (mail failing)\" (or \", n lost\") as a suffix, cut to one 160-char SMS part (fit_text, SMS_PART), never a bare \"alert mail FAILING\"; ChannelBook::note takes the event and host; Alerter::owed sends no second text for an alert already texted, and text_of suffixes every text while mail is in a failing run; WatchPeer gains a per-field `sustain` map (consecutive over-threshold readings before a class is distress, in place of fail_threshold), PeerState keeps per-class runs, SUSTAIN_DEFAULTS gives dropped_1m 10, a burst short of it logs \"not yet sustained; no alert\", and reminders name only sustained classes (16 Oct 2026: a scanner's bursts at birch, dropped_1m 215, were told as distress and the owner got only \"[steel:karri] alert mail FAILING (1 in a row)\"; red: test_a_failed_mail_falls_back_to_a_text_of_the_alert_00 got \"karri: alert mail FAILING\", a_drop_burst_is_not_distress_until_it_is_sustained fired at round 2; green: steel lib 340, with test_a_texted_alert_is_not_texted_again_when_its_mail_fails_00 and the stuck-mail-leg test now asserting one text)" |