1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
//! What:
//! The fail-closed failure of reading or recovering durable transaction state.
//! Why:
//! Malformed,
//! unsafe or contradictory state is never guessed at or deleted:
//! the command
//! stops with exit status 2 and a message naming the path,
//! and the state stays for
//! inspection (`CommitTransactionRecoveryError` in the incumbent;
//! implementation plan,
//! "Commit transactions and recovery").
//!
//! In TS you'd write (pseudocode):
//! ```ts
//! throw new CommitTransactionRecoveryError(`Unsafe transaction registry: ${root}`);
//! ```
/// What:
/// One recovery failure with its complete,
/// human-readable message.
/// A tuple-like `struct` holds one unnamed field.
/// Why:
/// Every site that fails closed knows what it found and where;
/// the message is the
/// whole diagnostic.
///
/// In TS you'd write (pseudocode):
/// ```ts
/// class CommitTransactionRecoveryError extends Error {}
/// ```
;
/// What:
/// The message as display text.
/// Why:
/// Diagnostics print the message unchanged.
///
/// In TS you'd write (pseudocode):
/// ```ts
/// error.message
/// ```
/// What:
/// A recovery failure for a filesystem step that failed.
/// Why:
/// One constructor names the step,
/// the path and the operating system's reason the same
/// way everywhere.
///
/// In TS you'd write (pseudocode):
/// ```ts
/// new CommitTransactionRecoveryError(`${operation} ${path} failed: ${error.message}`)
/// ```
/// Message controls stay out of the release executable.