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
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
//! What a pane's read or write came back as: the settings screen, a dog
//! toggle, and the secrets pane.
use super::*;
impl App {
/// `Msg::Settings`'s arm.
///
/// The screen opens on what this read found; a failed read leaves
/// the dashboard up. A landed write's re-read and `r` land here too,
/// with `body` already `Body::Settings`, so `opening` is false and
/// the cursor survives.
pub(super) fn on_settings(&mut self, result: Result<SettingsSnapshot, String>) -> Effect {
let opening = self.settings().is_none();
match result {
// A config pane opened while this read was in flight, so
// the operator asked for the pane AFTER asking for
// settings and this reply is the stale one. Adopting it
// would replace the pane with a settings screen the
// operator has moved on from, and leave `config_target`
// and `close_dialog` describing a screen that is no longer
// up. The `Body` enum stops the two coexisting; it does
// not stop this handler overwriting one with the other,
// which is the same race `on_sheep_config` had in the
// opposite direction.
Ok(_) if self.config_pane().is_some() => {}
Ok(snapshot) => {
// An action armed while the read was in flight: once
// the screen is up, `on_settings_key` no-ops `Confirm`
// and the prompt would be unreachable.
self.action = None;
// A filter box left open would keep eating every
// keystroke the settings keymap owns: `on_key` checks
// the mode first. The query itself is kept.
self.mode = InputMode::Normal;
// Reset to the top only while `opening`.
// `Settings::cursor` clamps on every read, so a
// preserved `Viewport` past a shorter dogs list
// still lands somewhere real.
let view = self.settings().map(|settings| settings.view.clone());
let mut settings = Settings::new(snapshot);
if !opening {
if let Some(view) = view {
settings.view = view;
}
let len = settings.rows().len();
settings.view.clamp(len);
}
self.body = Body::Settings(settings);
}
Err(message) => {
self.notice = Some(Notice::grave(message));
}
}
Effect::None
}
/// `Msg::SettingWritten`'s arm.
///
/// `Ok` re-reads rather than folding the write into the row, which
/// covers `Unset` too. `Err` reopens the editor for the two
/// free-text fields, so a long path need not be retyped.
///
/// Both arms act on the screen only when this reply is the one it
/// is waiting on. `Settings::resolve` answers that; a reply it
/// refuses still reports itself and still re-reads, but leaves
/// whatever is on screen alone. A dog section can also have
/// replaced the settings screen with a config pane while the
/// write was in flight, which `resolve` refuses for the same
/// reason: `InputMode::Text` with no editor behind it sends every
/// later keystroke to a text handler that owns nothing.
pub(super) fn on_setting_written(
&mut self,
edit: SettingEdit,
ticket: u64,
result: Result<(), String>,
) -> Effect {
let mine = self
.settings_mut()
.is_some_and(|settings| settings.resolve(ticket));
match result {
Ok(()) => self.reread_settings(),
Err(message) => {
// Split so no borrow of `self.body` is held across
// the `self.notice` assignment below.
if mine && let Some((field, buffer)) = typed_text_of(&edit) {
if let Some(settings) = self.settings_mut() {
settings.pending = Some(Pending::Typing { field, buffer });
}
// The overlay closes rather than the editor
// reopening beneath it. `on_key` checks text mode
// ahead of `keymap_open`, deliberately, so an `h`
// typed into a filter box stays a letter; the cost
// is that text mode restored from a MESSAGE would
// take the keyboard while the box is still drawn,
// and every key would reach a socket path the box
// hides. Reachable because `is_armed` does not
// cover `Pending::Sent`, so `h` with a write in
// flight opens the overlay instead of cancelling.
//
// Closing it is the lesser surprise: the operator
// asked for a key list, and what they get instead
// is their refused write, the grave notice saying
// why, and their own typed text back. `h` reopens
// the box.
self.keymap_open = false;
self.mode = InputMode::Text;
}
self.notice = Some(Notice::grave(message));
Effect::None
}
}
}
/// `Msg::DogPane`'s arm. The probe's own handling lives in
/// [`crate::lookout::app::dog_pane`]: this is the arm, so every pane
/// result reads through one file.
pub(super) fn on_dog_pane_answer(
&mut self,
name: String,
adopted_path: Option<PathBuf>,
result: Result<serde_json::Value, String>,
) -> Effect {
self.on_dog_pane(name, adopted_path, result)
}
/// `Msg::SheepDogNames`'s arm. The listing's own handling lives in
/// [`crate::lookout::app::pane_dogs`], for the same reason.
pub(super) fn on_sheep_dog_names_answer(
&mut self,
sheep: String,
ask: u64,
dogs: Vec<ListedDog>,
) -> Effect {
self.on_sheep_dog_names(&sheep, ask, dogs)
}
/// `Msg::SheepDog`'s arm, handled in [`crate::lookout::app::pane_dogs`].
pub(super) fn on_sheep_dog_answer(&mut self, sheep: &str, entry: SheepDogEntry) -> Effect {
self.on_sheep_dog(sheep, entry)
}
/// `Msg::DogWritten`'s arm.
///
/// `Ok` raises the daemon half: `Cycle` arms, `Confirm` writes the
/// file, this arm asks the shepherd. `Err` never reaches it, since
/// there is nothing for the daemon half to agree with.
///
/// `Ok` asks the shepherd whether or not the screen is still
/// waiting on this ticket: the file already says the dog is on or
/// off, so a daemon half dropped here would leave the two
/// disagreeing. `Err` clears only the prompt this ticket raised.
pub(super) fn on_dog_written(
&mut self,
edit: DogEdit,
ticket: u64,
result: Result<DogSource, String>,
) -> Effect {
match result {
Ok(source) => Effect::Send(Sent::Dog {
name: edit.name,
enable: edit.enable,
source,
ticket,
}),
Err(message) => {
if let Some(settings) = self.settings_mut() {
settings.resolve(ticket);
}
self.notice = Some(Notice::grave(message));
Effect::None
}
}
}
/// `Msg::Secrets`'s arm.
///
/// Dropped when the pane has since closed, the way a settings
/// read that outraced a config pane is: adopting it would reopen
/// a screen the operator has already left.
pub(super) fn on_secrets(
&mut self,
environment: String,
result: Result<Box<SecretsModel>, String>,
) -> Effect {
if let Body::Secrets(pane) = &mut self.body {
match result {
Ok(model) => {
// A fresh read describes the store as it is now;
// an arm from before it landed named a row this
// model may no longer even have.
pane.armed = None;
// Only on the very first load, where the pane's
// model is still the empty default and so has no
// tab yet: the daemon's own default environment
// wins the tab it lands on.
let first_load = pane.model.environments.is_empty();
if first_load {
pane.tab = model
.environments
.iter()
.position(|candidate| candidate == &environment)
.unwrap_or(0);
}
// The environments list is a union recomputed on
// every load and can shrink, so clamp a tab past
// the new end onto the last surviving one
// instead of dangling.
pane.tab = pane.tab.min(model.environments.len().saturating_sub(1));
// A selection on the trailing `+ new key`
// sentinel stays on it under the fresh model's
// own row count, rather than the ordinary clamp
// below, which would otherwise land it on the
// new model's last real row. Excludes the first
// load, whose own empty model reads `selected`
// (`0`) as that same sentinel by coincidence,
// having no rows yet either.
pane.selected = if !first_load && pane.selected_is_new_key_row() {
model.rows.len()
} else {
pane.selected.min(model.rows.len().saturating_sub(1))
};
pane.model = model;
// The row count clamp above says nothing about
// collapse state, and `collapsed` survives a
// reload: the surviving index can still name a
// row a still-folded namespace hides. Same
// fallback the `Collapse` arm uses.
if pane
.model
.rows
.get(pane.selected)
.is_some_and(|row| pane.is_collapsed(&row.source))
{
pane.move_by(0);
}
}
Err(message) => {
self.notice = Some(Notice::grave(message));
}
}
}
Effect::None
}
/// `Msg::Revealed`'s arm. The read's own handling lives in
/// [`crate::lookout::app::secrets_write`], for the same reason.
pub(super) fn on_revealed_answer(
&mut self,
key: String,
environment: String,
value: Option<RevealedValue>,
) -> Effect {
self.on_revealed(&key, &environment, value);
Effect::None
}
/// `Msg::SecretWritten`'s arm.
///
/// `Ok` re-reads (like `Msg::SettingWritten`) so the table shows
/// the file's new contents rather than what was typed, and clears
/// any revealed value, which belonged to the prior store. `Err`
/// raises no reload, so the table keeps its last known-good read.
pub(super) fn on_secret_written(&mut self, result: Result<bool, String>) -> Effect {
match result {
Ok(true) => {
self.hide_revealed();
Effect::LoadSecrets
}
// `secrets::unset` found no slot. Nothing changed, so
// nothing is re-read, and the operator hears about it: a
// destructive action reporting success over a no-op is the
// one answer this pane must never give.
Ok(false) => {
self.notice = Some(Notice::grave(NOTHING_REMOVED.to_string()));
Effect::None
}
Err(message) => {
self.notice = Some(Notice::grave(message));
Effect::None
}
}
}
}