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
//! What:
//! The words that tell a person how to change the push deadline, for the program that is running the push.
//! Why:
//! A push in a terminal reads `CLI_GIT_PUSH_DEADLINE_SECONDS` from that terminal's environment, but the resident commit
//! service pushes after the commit command returned and reads it from the environment the user manager gave the service
//! when it started, so advice to set the variable is not something a person can act on there. In the service the advice
//! names the user manager's own command and the restart that makes the service read the new value.
//!
//! In TS you'd write (pseudocode):
//! ```ts
//! const advice = inService ? 'run `systemctl --user set-environment ...` and then `systemctl --user restart ...`' : 'set VARIABLE';
//! ```
use super::bounded_push::PUSH_DEADLINE_VARIABLE;
use super::service_messages::RESTART_COMMAND;
use std::sync::atomic::{AtomicBool, Ordering};
/// The deadline the service advice gives as its example, in seconds.
pub const EXAMPLE_SECONDS: u32 = 120;
/// Whether this process is the resident commit service, which says so once at its start.
static IN_SERVICE: AtomicBool = AtomicBool::new(false);
/// Says that this process is the resident commit service, so that the advice it prints is the service's.
pub fn mark_service_process() {
IN_SERVICE.store(true, Ordering::SeqCst);
}
/// Whether this process is the resident commit service.
fn runs_in_service() -> bool {
return IN_SERVICE.load(Ordering::SeqCst);
}
/// The user manager's command that gives the service the variable at its next start.
fn set_command() -> String {
return format!("systemctl --user set-environment {PUSH_DEADLINE_VARIABLE}={EXAMPLE_SECONDS}");
}
/// What:
/// The clause that says how to allow a push more time, for the given program.
/// Why:
/// It reads after a semicolon or a comma in the messages of a stopped push.
///
/// In TS you'd write (pseudocode):
/// ```ts
/// extendClause(inService)
/// ```
pub fn extend_clause_for(service: bool) -> String {
if service {
return format!(
"run `{}` and then `{RESTART_COMMAND}` to allow longer (a variable set in a terminal never reaches the commit service)",
set_command()
);
}
return format!("set {PUSH_DEADLINE_VARIABLE} to allow longer");
}
/// What:
/// The clause that says what sets the push limit, for the given program.
/// Why:
/// The messages of a push that was not started or was stopped name the setting, and the setting is reached differently in
/// the service.
///
/// In TS you'd write (pseudocode):
/// ```ts
/// limitClause(inService)
/// ```
pub fn limit_clause_for(service: bool) -> String {
if service {
return extend_clause_for(true);
}
return format!("{PUSH_DEADLINE_VARIABLE} sets the limit");
}
/// The clause for allowing a push longer, in the program that is running.
pub fn extend_clause() -> String {
return extend_clause_for(runs_in_service());
}
/// The clause for what sets the push limit, in the program that is running.
pub fn limit_clause() -> String {
return limit_clause_for(runs_in_service());
}
/// Advice controls stay out of the release executable.
#[cfg(test)]
#[path = "push_deadline_advice_tests.rs"]
mod tests;