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
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
//! Registry of `EnvironmentConfig` parameters that are **accepted but not
//! yet implemented**.
//!
//! # Purpose
//!
//! Each entry in [`UNIMPLEMENTED_ENV_PARAMS`] names a config field that is
//! stored in `EnvironmentConfig` / `DbiEnvConfig` but is never read by any
//! production subsystem. [`warn_unimplemented_params`] is called from
//! [`crate::Environment::open`] and emits a `log::warn!` for each parameter
//! that has been set to a non-default value, preventing silent no-ops.
//!
//! # Adding a new parameter
//!
//! 1. Implement the parameter in the relevant subsystem (preferred), or
//! 2. Add an entry here with the field name and its default value expression.
//!
//! A `#[test]` in this module asserts that every entry triggers a warning when
//! set to a non-default value, so no new parameter can be silently added
//! without a corresponding registry entry.
//!
//! # Closing the gap (re-audit JE F-1)
//!
//! The parameters identified in the JE re-audit (2026-05-30) are listed
//! below. Each has been marked reserved in its rustdoc. As parameters are
//! wired to real features they are removed from this registry: `env_forced_yield`
//! and `env_latch_timeout_ms` were wired in 7.1 (JE `ENV_FORCED_YIELD` /
//! `ENV_LATCH_TIMEOUT`); `env_fair_latches` (JE `setFairLatches`) was wired
//! in this release via a per-latch `FairQueue` FIFO admission queue (see
//! `noxu-latch::fair_queue` and `.agent/notes-fair-latches.md`).
//!
//! # Graduation audit trail
//!
//! Each parameter that leaves this registry (because it became honored by a
//! production subsystem) is recorded here with the release and the test that
//! proves it is now consumed — the same discipline that let a prior audit catch
//! a stale entry:
//!
//! - `verify_schedule` — wired to the background verifier daemon.
//! - `env_forced_yield`, `env_latch_timeout_ms` — wired in 7.1.
//! - **`env_fair_latches`** — wired via `noxu-latch::fair_queue::FairQueue`, a
//! per-latch FIFO admission queue consulted from `ExclusiveLatch`'s and
//! `SharedLatch`'s acquire/release paths whenever the flag is set. Proven
//! honored by `crates/noxu-latch/tests/fair_latch_fifo_test.rs` (FIFO grant
//! order through the real latch types, flag on vs. off) and the
//! `noxu_shuttle`-gated `crates/noxu-latch/tests/shuttle_fair_latch.rs`
//! model. JE ref: `EnvironmentConfig.ENV_FAIR_LATCHES` / `setFairLatches`.
//! - **`env_expiration_enabled`, `env_ttl_clock_tolerance_ms`,
//! `cleaner_expiration_enabled` -- graduated in 7.5.4** when TTL / record
//! expiration was implemented end to end (put -> BIN/LN -> read-skip ->
//! cleaner reclaim -> recovery). Proven honored by
//! `crates/noxu-db/tests/ttl_expiration_test.rs` (expiry visibility, day
//! granularity, and recovery-survival) plus the tree/cleaner/recovery unit
//! coverage; JE refs `EnvironmentImpl.isExpired` / `BIN.isExpired` /
//! `ExpirationTracker` / `RecoveryManager.redo`.
//! - **`env_db_eviction` -- graduated in DBEVICT-1.** The prior entry claimed
//! 'per-database node eviction' (choosing which OPEN database's cached
//! pages get reclaimed first); that reading was WRONG and traced to a
//! `known-limitations.md` mischaracterisation. JE's actual semantics
//! (`EnvironmentConfig.ENV_DB_EVICTION` javadoc): eviction of metadata for
//! CLOSED databases -- gates whether a closed `DatabaseImpl`'s catalog
//! entry (name/config/root LSN) can leave `db_map` once nobody has it
//! open. Now wired in `EnvironmentImpl::close_database` /
//! `evict_closed_databases`; proven by the `dbevict1_*` tests in
//! `crates/noxu-dbi/src/environment_impl.rs` (closed-db eviction + reopen
//! reconstruction, and the in-use / `env_db_eviction=false` guards).
use crateEnvironmentConfig;
/// Describes one unimplemented `EnvironmentConfig` parameter.
/// The complete list of `EnvironmentConfig` parameters that are stored but
/// not consumed by any production subsystem in the current release.
///
/// Update this list whenever:
/// - A parameter is wired up (remove the entry), or
/// - A new reserved parameter is added (add an entry).
pub static UNIMPLEMENTED_ENV_PARAMS: & = &;
/// Emit a `log::warn!` for each unimplemented parameter that has been set to a
/// non-default value.
///
/// Called once from [`crate::Environment::open`] so operators immediately see
/// in the log that their config option has no effect.