onevcs_testing/state.rs
1//! What a provider knows, in a shape a journey can write down and read back.
2//!
3//! One state type per interface, shared by both flavours of it — the in-memory
4//! provider and the file-backed one differ in where the state lives and in nothing
5//! else, so a scenario seeded for one is the same scenario for the other.
6
7use std::collections::{BTreeMap, BTreeSet};
8
9use serde::{Deserialize, Serialize};
10
11use onevcs::rules::{Approvals, Drafts};
12use onevcs::{
13 ChangeId, ChangeRequest, Check, CheckSource, DraftReason, Error, Identity, Landed,
14 MergeOutcome, Recoverable, Result,
15};
16use onevcs::{MergePolicy, Publication, RequiredChecks, Session, SessionRequest, SessionToken};
17
18use crate::events;
19use crate::store::Checked;
20
21/// The version of the state document this build writes.
22///
23/// A file-backed state outlives the process that wrote it and is read by the next
24/// one, which makes it a stored contract like `onevcs`'s own registry document —
25/// and like that document, the version a document declares decides what is done
26/// with it rather than being guessed at. [`STATE_VERSION`] is the shape the goldens in
27/// `tests/golden/` hold, and those goldens are compared byte for byte, so a change
28/// to the document cannot reach a consumer without the diff saying so.
29///
30/// `2` was what both sides learned when publishing and closing a session came
31/// through the interface: [`VcsState::policy`], [`VcsState::closed_sessions`],
32/// [`VcsState::publications`], and [`HostState::titles`]. `3` is
33/// [`HostState::bodies`], the body a change request was opened with. `4` is the two
34/// fields a `Recoverable` gained inside [`VcsState::preserved`] — the live session
35/// holding a branch, and the lines it would land when it removes more than it adds.
36/// `5` is one more of those: whether the branch's work reached its base, and what
37/// says so. `6` is the two a `Check` gained inside [`HostState::checks`] — the
38/// commit the host attached that check to, and where the check is on the host. `7`
39/// is the two a draft change request needs — [`HostState::drafts`], the reason each
40/// change request was opened as a draft with, and [`HostState::made_ready`], the
41/// `ready_for_review` calls it took. `8` is the two an [`Identity`] inside
42/// [`VcsState::identities`] **lost** — `workflow` and `repo_type`, the registry's
43/// inferences from whether an origin had a host, which every decision they made now
44/// takes from the resolved publication policy instead. `9` is the draft reason inside
45/// [`HostState::drafts`] becoming one of two kinds and saying which — `kind` is
46/// `awaiting-release` or `held` — and [`HostState::described`], the descriptions a
47/// host was handed for a change request after it was opened. `10` is the failure
48/// vocabulary a publication's outcome inside [`VcsState::publications`] may name
49/// widening by one kind, `host-prerequisite` — no field moved, but a document naming
50/// it is one a version 9 build cannot read, and the version is how it says so. `11` is
51/// one more field a `Recoverable` gained inside [`VcsState::preserved`], the same way
52/// `4` and `5` were: where `onevcs preserve` put that branch on its identity's origin,
53/// and the commit the origin carries it at. `12` is the labels a session is opened
54/// with — [`VcsState::session_labels`], keyed by token the way its identity is — and
55/// the two fields a `Recoverable` gained inside [`VcsState::preserved`] to carry them:
56/// the session that answers for the row, and that session's labels. `13` is one more
57/// field a `Recoverable` gained there: the branch's retirement classification — whether
58/// it provably holds nothing beyond its base, was superseded by a retry that landed, or
59/// is kept, and the evidence for it. No provider here classifies a row, so a row this
60/// crate writes carries none; a scenario may seed one. `14` is the draft lifecycle:
61/// [`HostState::awaiting_checks`], the change requests opened as a draft while their
62/// required checks run, [`HostState::checks_after_lift`], the checks a host registers
63/// only once a change is lifted, and [`HostState::required_checks`], what the host
64/// says a merge into a base requires — beside [`VcsState::approvals`] and
65/// [`VcsState::drafts`], the two policy fields a provider's publication now routes
66/// the lifecycle on. A publication outcome inside [`VcsState::publications`] may also
67/// be `change-review-draft`. `15` is the field a `Session` gained inside
68/// [`VcsState::sessions`]: `conflict`, the merge a continued branch's session opened
69/// over and left in progress. No provider here merges a base into a branch, so a
70/// session this crate opens carries none; a scenario may seed one. `16` is the failure
71/// vocabulary a publication's outcome inside [`VcsState::publications`] may name
72/// widening by one kind, `cancelled`, the way `10` widened it — no field moved, but a
73/// document naming it is one a version 15 build cannot read. No provider here waits on
74/// anything, so a publication this crate runs is never cancelled; a scenario may seed
75/// one. `17` is the field a `Retirement` gained inside a row of
76/// [`VcsState::preserved`]: `cause`, the read that failed for a branch kept as
77/// `unknown`, which every retirement writes — `null` for every other reason. No
78/// provider here classifies a branch, so a row this crate writes carries none; a
79/// scenario may seed one. `18` is what the record of a gate run and of a landing needs
80/// from a host: the field a `Check` gained inside [`HostState::checks`] —
81/// `completed_at`, when the host says that run completed — and
82/// [`HostState::merge_times`], when each merge this host performed reached its base.
83///
84/// **Every change to the document is versioned, an added field included.** A field
85/// that only ever appears when it holds something is *compatible* — that is what
86/// [`OLDEST_READABLE_VERSION`] is for — but compatible is not the same as
87/// unremarkable: the version is how a consumer's checked-in scenario says which
88/// shape it was written against, and a document that gained a field without saying
89/// so leaves nothing able to tell "this build wrote no body" from "this document
90/// predates bodies". The two answers differ for exactly the journey this crate
91/// exists to support.
92/// `19` adds the recovery branch tip; older rows default it to `None`.
93pub const STATE_VERSION: u32 = 19;
94
95/// The oldest document version this build reads.
96///
97/// Every version from here to [`STATE_VERSION`] is read and carried forward on the
98/// way in, which is how `onevcs`'s own registry document treats its older
99/// versions: what separates a readable older version from a refused one is whether
100/// its every field still means here what it meant there. `2` to `3` added a field
101/// and changed none, so a version 2 document reads as one whose change requests
102/// were opened with no body — which is what they were; `3` to `4` added two the same
103/// way, so a version 3 document reads as one whose preserved rows say nothing about a
104/// hold or a line count, which is what they said. `4` to `5` added one that every row
105/// answers rather than one that appears when it holds something, so a version 4
106/// document's rows are carried forward as the answer that list *was*: preserved work
107/// nobody published, which is work that did not land. `5` to `6` added two that
108/// appear only when they hold something, so a version 5 document's checks read as
109/// checks whose commit and address that build never recorded — which is what they
110/// were, and the one thing that must not be filled in from the change request's own
111/// head. `6` to `7` added two more of that kind, so a version 6 document reads as one
112/// whose change requests were opened before this crate could draft one — which is what
113/// they were: no draft reason recorded for any of them, and no lift ever asked for.
114/// `7` to `8` *removed* two from each identity, and a version 7 document reads past
115/// them: an identity is its origin and its gate here as it is in `onevcs`, and the two
116/// keys beside them are ones this build has no opinion on. `8` to `9` gave every
117/// draft reason a `kind`, and a reason written without one is read as the one kind
118/// there was — `awaiting-release`, whose four fields it carries unchanged — which is
119/// `drafts_of_any_version`'s whole job; the descriptions beside it are absent from a
120/// document written before them, which is the answer, since that build could describe
121/// nothing. `9` to `10` changed no field and no meaning: every failure kind a version 9
122/// document can hold is spelled here as it was there and means what it meant, so it
123/// reads unchanged and needs no carrying forward beyond its version. `10` to `11` added
124/// one that appears only when it holds something, so a version 10 document's preserved
125/// rows read as rows saying nothing about an origin — which is what they said, since
126/// that build had no verb that could put a branch on one. `11` to `12` added the
127/// labels, which appear only where a session was opened with some, and the two row
128/// fields that carry them, which a version 11 row reads as absent: a session nobody
129/// labelled, and a row that names no session — which is what that build's rows said,
130/// since it recorded neither. `12` to `13` added the row's retirement, which appears only
131/// where a row holds one, so a version 12 row reads as one nothing classified — which
132/// is what it was, since that build had no classification to record. `13` to `14`
133/// added fields that appear only when they hold something, so a version 13 document
134/// reads as one whose change requests were opened before the lifecycle drafted any,
135/// whose checks never change on a lift, whose host declares its required checks by
136/// the checks it was seeded with, and whose policy leaves approvals and drafts at
137/// their defaults — which is what that build published under. `14` to `15` added the
138/// session's conflict, which appears only where a session holds one, so a version 14
139/// document's sessions read as sessions that opened clean — which is what they were,
140/// since that build opened none over a merge. `15` to `16` changed no field and no
141/// meaning, as `9` to `10` did not: every failure kind a version 15 document can hold is
142/// spelled here as it was there, so it reads unchanged. `16` to `17` added the
143/// retirement's cause, which a version 16 retirement reads as `null` — which is what it
144/// said, since that build named no read that failed. `17` to `18` added two fields that
145/// appear only when they hold something, so a version 17 document's checks read as
146/// checks whose completion that build never recorded, and its merges as merges whose
147/// time it never recorded — which is what they were.
148///
149/// `1` is refused rather than read for the opposite reason: it describes a provider
150/// that could not publish, and every session in it would read back as open — a
151/// wrong answer where a journey asserting on a session it had closed needs a
152/// refusal.
153pub const OLDEST_READABLE_VERSION: u32 = 2;
154
155/// Everything the repository side of a run knows about itself.
156///
157/// Every field is public and serializable, so a journey both seeds a scenario and
158/// asserts on what a run left behind. Everything but the version is omitted when
159/// it holds nothing, so a hand-written document names only the part of a scenario
160/// that matters — and a document written by a build that knew fewer fields still
161/// reads here.
162#[derive(Debug, Clone, Serialize, Deserialize)]
163#[serde(default)]
164pub struct VcsState {
165 /// The schema version this state was written at. A document that names none is
166 /// the one this build writes.
167 // llmlint: ignore[boundary_inputs_validated] deciding what to do with a version this
168 // build does not read is the whole of the check — and it is in `Checked::check` below,
169 // where a document is read, rather than here where serde only proves the shape.
170 pub version: u32,
171 /// The repository identities this provider can resolve. A
172 /// [`SessionRequest::repo`] naming none of them is refused, the way an
173 /// unregistered repository is.
174 #[serde(skip_serializing_if = "Vec::is_empty")]
175 pub identities: Vec<Identity>,
176 /// Every session opened or seeded, in the order they were opened.
177 #[serde(skip_serializing_if = "Vec::is_empty")]
178 pub sessions: Vec<Session>,
179 /// Which identity each session belongs to.
180 ///
181 /// Beyond the sketch this crate was specified from, and unavoidable: a
182 /// [`Session`] carries no identity, and a [`Recoverable`] must name one — so
183 /// preserving a session's branch could not answer the question `recoverable`
184 /// asks without this. `open_session` records it; nothing else writes it.
185 // llmlint: ignore[invalid_states_unrepresentable] an identity key is a `String`
186 // everywhere the crate this mirrors spells one — `Recoverable.identity`,
187 // `Identity.origin`, the registry document's own map key — and a newtype here would
188 // make a seeded state disagree with the types it is made of. Every value written to
189 // this map came out of `identity_of`, so it names an identity this provider holds.
190 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
191 pub session_identities: BTreeMap<SessionToken, String>,
192 /// The labels each session was opened with, for the sessions opened with any.
193 ///
194 /// Keyed by token the way [`session_identities`](Self::session_identities) is,
195 /// and for the same reason: a [`Session`] carries no labels, and both `session
196 /// holders` and every `recoverable` row report them. `open_session` records
197 /// them; nothing else writes it.
198 // llmlint: ignore[invalid_states_unrepresentable] keyed by session token, exactly as
199 // `session_identities` above is and for the same reason it gives.
200 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
201 pub session_labels: BTreeMap<SessionToken, BTreeMap<String, String>>,
202 /// Preserved work, newest last, as `recoverable` reports it.
203 ///
204 /// [`Recoverable`] rather than `PreservedBranch` — it *contains* the preserved
205 /// branch and adds the identity, the checkout, why the workstream stopped, and
206 /// the command that lands it, none of which are derivable from the branch
207 /// alone. One list rather than two that could disagree.
208 #[serde(skip_serializing_if = "Vec::is_empty")]
209 pub preserved: Vec<Recoverable>,
210 /// The sessions that have been closed. Every other session here is open.
211 ///
212 /// One way to say closed rather than two, so a scenario written by hand names
213 /// only the sessions whose lifecycle is not the one they were opened in.
214 // llmlint: ignore[invalid_states_unrepresentable] keyed by session token, exactly as
215 // `session_identities` above is and for the same reason: this document is a scenario
216 // somebody writes by hand, and a session is named once under `sessions` with the rest
217 // of the state keyed to it rather than nested inside a shape that could hold only one
218 // arrangement. A token here that names no opened session is refused in
219 // `Checked::check`, where the document is read — the same trust boundary every other
220 // cross-reference in it is checked at.
221 #[serde(skip_serializing_if = "BTreeSet::is_empty")]
222 pub closed_sessions: BTreeSet<SessionToken>,
223 /// The policy this provider publishes under.
224 ///
225 /// The answer a rules file gives the real implementation, which a provider has
226 /// none of — so a journey states it, and unset is the policy the contract's own
227 /// `default:` names ([`DEFAULT_PUBLICATION`](crate::DEFAULT_PUBLICATION)). A
228 /// per-run policy narrows it through [`MergePolicy::narrow`], which is the
229 /// rules system's rule rather than a restatement of it here.
230 #[serde(skip_serializing_if = "Option::is_none")]
231 pub policy: Option<MergePolicy>,
232 /// Whether this provider's changes need an approval, which is the other half of
233 /// what decides a green draft's ending: `change-open` with approvals required
234 /// keeps it for its user's review. Unset is the contract's own `default:`,
235 /// [`DEFAULT_APPROVALS`](crate::DEFAULT_APPROVALS).
236 #[serde(skip_serializing_if = "Option::is_none")]
237 pub approvals: Option<Approvals>,
238 /// The `drafts:` a rules file would give this provider's identity. Unset, and
239 /// each key it leaves unset, is the shipped default: the lifecycle on and the
240 /// early-lift warning on.
241 #[serde(skip_serializing_if = "Option::is_none")]
242 pub drafts: Option<Drafts>,
243 /// Every publication this provider performed, in the order it performed them.
244 ///
245 /// Both a record a journey asserts on and the answer to "has this session been
246 /// published already": a second publication of a session that landed has
247 /// nothing the base does not already carry, which is what the real
248 /// implementation reports for the same reason.
249 // llmlint: ignore[invalid_states_unrepresentable] this holds `onevcs::Publication`
250 // verbatim — the value `Vcs::publish` handed back, carrying its own session and branch
251 // — so a journey asserts on exactly what a caller would receive. A shape that made
252 // "this publication is of some other session's branch" unrepresentable could not hold
253 // that type, and would be a second spelling of the answer the crate next door already
254 // has. The cross-reference is checked in `Checked::check` instead, where the document
255 // is read.
256 #[serde(skip_serializing_if = "Vec::is_empty")]
257 pub publications: Vec<Publication>,
258}
259
260/// A repository side that knows nothing, at the version this build writes.
261impl Default for VcsState {
262 fn default() -> Self {
263 Self {
264 version: STATE_VERSION,
265 identities: Vec::new(),
266 sessions: Vec::new(),
267 session_identities: BTreeMap::new(),
268 session_labels: BTreeMap::new(),
269 preserved: Vec::new(),
270 closed_sessions: BTreeSet::new(),
271 policy: None,
272 approvals: None,
273 drafts: None,
274 publications: Vec::new(),
275 }
276 }
277}
278
279/// Everything the remote-host side of a run knows about itself.
280///
281/// Omitted-when-empty and versioned for the same reasons [`VcsState`] is.
282#[derive(Debug, Clone, Serialize, Deserialize)]
283#[serde(default)]
284pub struct HostState {
285 /// The schema version this state was written at. A document that names none is
286 /// the one this build writes.
287 // llmlint: ignore[boundary_inputs_validated] as on `VcsState::version`: the decision
288 // about an unreadable version is made in `Checked::check`, where the document is read.
289 pub version: u32,
290 /// Who the host says is calling. Empty is refused, exactly as a `gh` that
291 /// reports no authenticated user is.
292 // llmlint: ignore[invalid_states_unrepresentable] the interface this satisfies is
293 // `authenticated_user() -> Result<String>`, so the login is a `String` by contract and
294 // the one unusable value — a host that names nobody — is refused where it is read
295 // rather than made unrepresentable in a state a journey writes by hand.
296 pub authenticated_user: String,
297 /// Every change request that has been opened or seeded.
298 #[serde(skip_serializing_if = "Vec::is_empty")]
299 pub changes: Vec<ChangeRequest>,
300 /// The head branch each change request was opened from.
301 ///
302 /// Beyond the sketch, and unavoidable: [`ChangeRequest`] records only the base
303 /// it targets, and `find_changes` matches on the head as well.
304 // llmlint: ignore[invalid_states_unrepresentable] the matching `ChangeSpec.head` and
305 // `ChangeRequest.base` are `String` in the contract this mirrors, and a validated ref
306 // type here would disagree with them. Every value written to this map went through
307 // `addressable` in `open_change` first, which is the same refusal the real
308 // implementation makes at the same point.
309 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
310 pub heads: BTreeMap<ChangeId, String>,
311 /// The title each change request was opened under.
312 ///
313 /// Beyond the sketch, and for the same reason [`heads`](HostState::heads) is:
314 /// [`ChangeRequest`] records neither, and the title is what a publication's
315 /// commit subject becomes — so a journey asserting that the subject it asked
316 /// for is the one the host was given has nowhere else to read it.
317 // llmlint: ignore[invalid_states_unrepresentable] this records the `ChangeSpec.title`
318 // the contract fixes as a `String`, so a validated type here would disagree with the
319 // one it mirrors. `Subject` is not that type: it is `onevcs`'s rule for a *commit
320 // subject*, and a host's own limit is its own — spelling it here would
321 // refuse a seeded title a real host accepts, which is drift in the direction that
322 // looks like rigour. What the host itself refuses is a title that names nothing, and
323 // that is refused below and in `open_change`, at the boundary the value arrives at.
324 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
325 pub titles: BTreeMap<ChangeId, String>,
326 /// The body each change request was opened with, for the change requests that
327 /// were opened with one.
328 ///
329 /// Beside [`titles`](HostState::titles) and for its reason: the body is what a
330 /// caller passes on the `PublishRequest` and nothing else records it, so a
331 /// journey asserting that the body it drafted is the one the host was given has
332 /// nowhere else to read it. A change request with no entry was opened with no
333 /// body at all, which is what a publication nobody gave one does — the two are
334 /// different scenarios, and an empty string is the first rather than the second.
335 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
336 pub bodies: BTreeMap<ChangeId, String>,
337 /// The checks the host reports on each change request. A change with no entry
338 /// has no checks, which is what a repository with no CI reports.
339 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
340 pub checks: BTreeMap<ChangeId, Vec<Check>>,
341 /// The log the host hands over for a check, keyed by change request and then by
342 /// check name. Beyond the sketch: `check_log` is one of the six methods, and
343 /// without this the only log a journey could asssert on is a synthesized one.
344 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
345 pub check_logs: BTreeMap<ChangeId, BTreeMap<String, String>>,
346 /// The reason each change request that was opened as a **draft** was drafted
347 /// with, for the change requests that were.
348 ///
349 /// Beside [`bodies`](HostState::bodies) and for its reason: the reason is what a
350 /// caller passes on the `PublishRequest` and this is where a journey reads back
351 /// that the host was given it. A change with no entry is not a draft, which is
352 /// what every change request opened without one is.
353 ///
354 /// Nothing is refused about the reason itself here. Its shape — that every field
355 /// of it renders as the one line it is printed on — is `onevcs`'s own rule, and
356 /// it is applied where a publication takes one in, before any host is asked.
357 #[serde(
358 skip_serializing_if = "BTreeMap::is_empty",
359 deserialize_with = "drafts_of_any_version"
360 )]
361 pub drafts: BTreeMap<ChangeId, DraftReason>,
362 /// Every `ready_for_review` call this host has taken, in the order it took them
363 /// — the lifts it was asked to perform, never a request for a *reviewer*.
364 ///
365 /// A list rather than a set, and beyond the sketch for a reason a set could not
366 /// serve: lifting a draft is required to be *idempotent*, so what a journey
367 /// asserts is that a second publication asked the host for nothing — and only a
368 /// record of the calls themselves can say that. A change named here is not a
369 /// draft any more, whatever [`drafts`](HostState::drafts) says it was opened as.
370 #[serde(skip_serializing_if = "Vec::is_empty")]
371 pub made_ready: Vec<ChangeId>,
372 /// The change requests opened as a draft **while their required checks run** —
373 /// the lifecycle's draft, which no caller gave a reason for and so is not in
374 /// [`drafts`](HostState::drafts). A change named here is a draft until
375 /// [`made_ready`](HostState::made_ready) names it.
376 #[serde(skip_serializing_if = "BTreeSet::is_empty")]
377 pub awaiting_checks: BTreeSet<ChangeId>,
378 /// The checks the host reports on a change request once it has been lifted out of
379 /// its draft, in place of [`checks`](HostState::checks).
380 ///
381 /// What a repository whose workflow skips drafts looks like from outside: the
382 /// draft's checks are skipped or absent, and the run the lift triggers registers
383 /// after it. A change with no entry reports the same checks either side of a lift.
384 ///
385 /// A publication tells the run a lift triggered from the draft's by the run's own
386 /// identity, as it would on a real host: a check named here that the draft also
387 /// reported is a new run — running or settled — only where its
388 /// [`started_at`](Check::started_at) is one no draft-era run of that check reported. So seed a re-run with a start of its own — an entry repeating
389 /// the draft's start, or reporting none, is the draft's run still standing.
390 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
391 pub checks_after_lift: BTreeMap<ChangeId, Vec<Check>>,
392 /// What this host answers when asked which checks a merge into a base requires.
393 ///
394 /// Unset is a host whose branch protection names exactly the checks it was seeded
395 /// as required, on any change request — a complete answer, and an empty one where
396 /// none is seeded required. Seeded, it is the answer for every base: an empty
397 /// complete one is a repository declaring no required check, and one naming an
398 /// `unconsulted` source is the incomplete answer a narrower credential gets.
399 #[serde(skip_serializing_if = "Option::is_none")]
400 pub required_checks: Option<RequiredChecks>,
401 /// Every `describe_change` call this host has taken, in the order it took them:
402 /// which change request, the title it was handed when it was handed one, and the
403 /// body.
404 ///
405 /// The calls themselves, for the reason [`made_ready`](HostState::made_ready) is:
406 /// what a journey asks is what a closeout *wrote*, call by call, and the current
407 /// title and body — which each call also writes into
408 /// [`titles`](HostState::titles) and [`bodies`](HostState::bodies), so
409 /// `change_description` answers from the same record `open_change` wrote — can
410 /// only say where the description ended up.
411 #[serde(skip_serializing_if = "Vec::is_empty")]
412 pub described: Vec<Described>,
413 /// Which sources this host answers about its checks from, which is what the
414 /// real implementation reports alongside them.
415 ///
416 /// Unset is a credential allowed to read everything: the whole rollup, exactly
417 /// what a host with nothing to hide reports. A journey states a narrower set to
418 /// be the credential the real one meets in CI — a fine-grained token, which
419 /// cannot read check runs at all and sees GitHub Actions and nothing else — and
420 /// states an *empty* one to be a credential that can read no source at all,
421 /// which is a refusal rather than "no checks". Unset and empty are therefore
422 /// different scenarios, which is why this is an `Option` rather than a set whose
423 /// emptiness means "not stated".
424 #[serde(skip_serializing_if = "Option::is_none")]
425 pub check_sources: Option<BTreeSet<CheckSource>>,
426 /// What merging each change request did.
427 ///
428 /// Both a script and a record: an entry seeded here is what `merge` answers,
429 /// whatever the policy asks for — which is how a journey expresses a host that
430 /// queues or refuses — and a merge the policy decided is written back here.
431 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
432 pub merges: BTreeMap<ChangeId, MergeOutcome>,
433 /// When each merged change request reached its base, as this host spells the
434 /// moment — what `merge_time` answers.
435 ///
436 /// Written beside [`merges`](HostState::merges) whenever this host performs a
437 /// merge, at the moment it performs it, and seedable for a merge a journey
438 /// seeded: a host that merged on its own clock, earlier than anybody asked, is
439 /// exactly what a late merge's record must report the time of. A merged change
440 /// with no entry is one whose time this host cannot say.
441 // llmlint: ignore[invalid_states_unrepresentable] this mirrors the answer
442 // `RemoteHost::merge_time` gives, which the contract fixes as the host's own spelling
443 // in an `Option<String>`; a timestamp type here would disagree with the seam it
444 // answers. A value that is not an RFC3339 moment is refused in `check`, where the
445 // document is read, and every one this host writes is `events::timestamp`'s.
446 #[serde(skip_serializing_if = "BTreeMap::is_empty")]
447 pub merge_times: BTreeMap<ChangeId, String>,
448}
449
450/// One description a host was handed for a change request after it was opened.
451///
452/// What `RemoteHost::describe_change` was given, verbatim: the title only where the
453/// call carried one, because a call that replaced the body alone left the title as
454/// it was, and a record that filled it in would say the caller wrote a title nobody
455/// wrote.
456// llmlint: ignore[invalid_states_unrepresentable] the title and body are the `&str`s the
457// seam hands over — a host places no shape on prose, and `onevcs`'s own `Subject` rule
458// was applied where the description was composed, before any host was asked.
459#[derive(Debug, Clone, PartialEq, Eq, Serialize, Deserialize)]
460pub struct Described {
461 /// The change request the description was written to.
462 pub id: ChangeId,
463 /// The title the call replaced the change request's with, when it replaced one.
464 #[serde(default, skip_serializing_if = "Option::is_none")]
465 pub title: Option<String>,
466 /// The body the call replaced the change request's with.
467 pub body: String,
468}
469
470/// The `drafts` map of a document at any readable version.
471///
472/// A document written before version 9 spells a draft reason as the four fields of
473/// the one kind there was and no `kind` beside them; this build's reason is one of
474/// two kinds and says which. So a reason arriving without a `kind` is read as
475/// `awaiting-release` — exactly what it was — rather than refused, which is what
476/// keeps a consumer's checked-in scenario readable across the bump. A reason that
477/// *names* a kind is read as it names it, so nothing written by this build is
478/// reinterpreted.
479fn drafts_of_any_version<'de, D>(
480 deserializer: D,
481) -> std::result::Result<BTreeMap<ChangeId, DraftReason>, D::Error>
482where
483 D: serde::Deserializer<'de>,
484{
485 let raw: BTreeMap<ChangeId, serde_json::Map<String, serde_json::Value>> =
486 Deserialize::deserialize(deserializer)?;
487 raw.into_iter()
488 .map(|(id, mut fields)| {
489 fields
490 .entry("kind")
491 .or_insert_with(|| serde_json::Value::from("awaiting-release"));
492 serde_json::from_value::<DraftReason>(serde_json::Value::Object(fields))
493 .map(|reason| (id, reason))
494 .map_err(serde::de::Error::custom)
495 })
496 .collect()
497}
498
499/// Who a host with nothing seeded says is calling.
500///
501/// A host that answers nobody is refused by the real implementation, so a default
502/// state that answered nobody would be a provider that cannot run a publication
503/// until it is configured.
504pub const DEFAULT_AUTHENTICATED_USER: &str = "onevcs-testing";
505
506impl Default for HostState {
507 fn default() -> Self {
508 Self {
509 version: STATE_VERSION,
510 authenticated_user: DEFAULT_AUTHENTICATED_USER.to_owned(),
511 changes: Vec::new(),
512 heads: BTreeMap::new(),
513 titles: BTreeMap::new(),
514 bodies: BTreeMap::new(),
515 drafts: BTreeMap::new(),
516 made_ready: Vec::new(),
517 awaiting_checks: BTreeSet::new(),
518 checks_after_lift: BTreeMap::new(),
519 required_checks: None,
520 described: Vec::new(),
521 checks: BTreeMap::new(),
522 check_logs: BTreeMap::new(),
523 check_sources: None,
524 merges: BTreeMap::new(),
525 merge_times: BTreeMap::new(),
526 }
527 }
528}
529
530/// The identity a session request names, or the reason none of them is it.
531///
532/// Three ways to name one, mirroring what the registry accepts: the identity key
533/// itself, the `owner/name` tail of it, or the bare repository name.
534pub(crate) fn identity_of<'a>(state: &'a VcsState, origin_or_path: &str) -> Option<&'a Identity> {
535 let wanted = origin_or_path.trim_end_matches('/');
536 state
537 .identities
538 .iter()
539 .find(|identity| identity.origin == wanted)
540 .or_else(|| {
541 state.identities.iter().find(|identity| {
542 identity
543 .origin
544 .rsplit('/')
545 .next()
546 .is_some_and(|name| name == wanted)
547 || identity.origin.ends_with(&format!("/{wanted}"))
548 })
549 })
550}
551
552/// The known identities, as a refusal names them.
553pub(crate) fn known(state: &VcsState) -> String {
554 if state.identities.is_empty() {
555 return "this provider was seeded with no identities".to_owned();
556 }
557 let names: Vec<&str> = state
558 .identities
559 .iter()
560 .map(|identity| identity.origin.as_str())
561 .collect();
562 format!("it knows {}", names.join(", "))
563}
564
565/// The identity a session belongs to, or the reason this provider cannot say.
566///
567/// `open_session` records it and nothing else writes it, so a session that arrived
568/// in a hand-written scenario without one is refused here rather than published
569/// against a repository nobody named.
570pub(crate) fn identity_for(state: &VcsState, token: &SessionToken) -> Result<String> {
571 state
572 .session_identities
573 .get(token)
574 .cloned()
575 .ok_or_else(|| Error::Invalid {
576 reason: format!(
577 "this provider has no record of session {:?}, so it cannot say which identity \
578 its work belongs to",
579 token.0
580 ),
581 })
582}
583
584/// The session a token names.
585pub(crate) fn session_of<'a>(state: &'a VcsState, token: &SessionToken) -> Option<&'a Session> {
586 state
587 .sessions
588 .iter()
589 .find(|session| session.token == *token)
590}
591
592/// The branch a request asks for, or the one that is derived from the token.
593///
594/// `branch` and `branch_name` are two answers to one question — *continue this* and
595/// *cut one at this* — so a request naming both is refused here as the real
596/// implementation refuses it: that refusal is about the shape of the request rather
597/// than about anything a repository does, and a consumer proving it must meet the
598/// same answer on either side.
599///
600/// **What a provider deliberately does not do to `branch_name` is the rest**, and it
601/// is not approximated: the host's branch prefix is read out of an `onevcs` state
602/// root no provider has, and the first-free suffix is searched against an identity's
603/// checkouts and its origin, which a provider has neither of. So the name is taken as
604/// it was proposed and refused — naming it — where git would refuse it, rather than
605/// being sanitized by a second copy of a grammar that would then have to be held to
606/// the first. A consumer proving what the prefix, the sanitizer and the collision
607/// suffix do drives the real `onevcs`, which is where all three live.
608pub(crate) fn requested_branch(req: &SessionRequest, token: &SessionToken) -> Result<String> {
609 if let (Some(pinned), Some(proposed)) = (&req.branch, &req.branch_name) {
610 return Err(Error::Invalid {
611 reason: format!(
612 "this request names both a branch to continue ({pinned:?}) and a name to cut \
613 ({proposed:?}), which are two answers to one question"
614 ),
615 });
616 }
617 let name = req
618 .branch
619 .clone()
620 .or_else(|| req.branch_name.clone())
621 .unwrap_or_else(|| format!("onevcs/{}", token.0));
622 named_branch(&name, "the branch")?;
623 Ok(name)
624}
625
626/// A branch name, refused here if git would refuse it.
627///
628/// The real implementation asks `git check-ref-format`, which is the parser that
629/// decides; a provider with no git carries `git-check-ref-format(1)`'s rules
630/// instead. That is a restatement, so it is gated rather than trusted:
631/// `refs.rs` in the suite runs both this and git itself over a table of names
632/// and holds them to each other, because a copy of somebody else's grammar with
633/// no gate is a copy that drifts.
634///
635/// One deliberate difference, and the gate knows about it: a leading `-` is
636/// refused here even though git accepts it as a ref, because such a name reaches
637/// a command line as an option rather than as the branch it spells.
638pub(crate) fn named_branch(value: &str, what: &str) -> Result<()> {
639 // Rule 1 is per slash-separated component; the rest are about the whole name.
640 let components_usable = !value.is_empty()
641 && value.split('/').all(|component| {
642 !component.is_empty() && !component.starts_with('.') && !component.ends_with(".lock")
643 });
644 let usable = components_usable
645 && !value.starts_with('-')
646 && !value.contains("..")
647 && !value.contains("@{")
648 && !value.ends_with('.')
649 && !value.ends_with('/')
650 && !value.chars().any(|c| {
651 c.is_whitespace() || c.is_ascii_control() || c == '\u{7f}' || "~^:?*[\\".contains(c)
652 });
653 if !usable {
654 return Err(Error::Invalid {
655 reason: format!("{what} {value:?} is a name git would not accept"),
656 });
657 }
658 Ok(())
659}
660
661/// A label, refused here where the real implementation refuses one: a key is one or
662/// more of `A-Z`, `a-z`, `0-9`, `_` and `-`, and a value is one line. The same rule
663/// spelled twice on purpose, for the reason [`named_branch`] gives — a provider with
664/// no `onevcs` state root carries the grammar, and the journeys over both providers
665/// hold the two to each other.
666pub(crate) fn label_pair(key: &str, value: &str) -> Result<()> {
667 let key_usable = !key.is_empty()
668 && key
669 .chars()
670 .all(|c| c.is_ascii_alphanumeric() || c == '_' || c == '-');
671 if !key_usable {
672 return Err(Error::Invalid {
673 reason: format!(
674 "{key:?} is not a label key; a key is one or more of A-Z, a-z, 0-9, `_` and `-`"
675 ),
676 });
677 }
678 if value.contains('\n') {
679 return Err(Error::Invalid {
680 reason: format!(
681 "the value of label {key:?} holds a newline; a label's value is one line"
682 ),
683 });
684 }
685 Ok(())
686}
687
688/// A seeded repository side is refused if it holds a session nothing could act on.
689impl Checked for VcsState {
690 fn check(&self) -> Result<()> {
691 readable_version(self.version)?;
692 for session in &self.sessions {
693 // The token names a file under the state root, and a branch goes on to
694 // spell a ref; both arrive from whoever wrote the document.
695 if !events::is_safe_name(&session.token.0) {
696 return Err(Error::Invalid {
697 reason: format!("{:?} is not a session token", session.token.0),
698 });
699 }
700 named_branch(&session.branch, "the branch")?;
701 named_branch(&session.base, "the base")?;
702 }
703 for row in &self.preserved {
704 known_identity(self, &row.identity, "preserved work")?;
705 named_branch(&row.branch.branch, "the preserved branch")?;
706 named_branch(&row.branch.base, "the preserved branch's base")?;
707 // A hold that names a session is checked like the three below: a row
708 // held by a session nobody opened is the same fiction, and the costly one
709 // — it is the session an operator is told to wait for or close. A running
710 // publication holds a branch under no session and names none.
711 if let Some(token) = row.held_by.as_ref().and_then(|held| held.token.as_ref()) {
712 opened(self, token, "holding preserved work")?;
713 }
714 }
715 // Both of these name a session, so both are checked twice over: the token
716 // has to be a plain name, because it goes on to spell the file its stream is
717 // written in, and it has to name a session this state actually holds. A
718 // document that closes or publishes a session nobody opened describes a run
719 // that could not have happened, and answering `recoverable` or `session`
720 // from it would be answering from a fiction rather than refusing one.
721 for token in &self.closed_sessions {
722 opened(self, token, "closed")?;
723 }
724 for (token, labels) in &self.session_labels {
725 opened(self, token, "labelled")?;
726 for (key, value) in labels {
727 label_pair(key, value)?;
728 }
729 }
730 for (token, origin) in &self.session_identities {
731 opened(self, token, "given an identity")?;
732 // The value as well as the key: this is what `identity_for` answers with,
733 // and it goes on to spell the slug a change request is opened against and
734 // the label every one of that session's events carries. An identity this
735 // provider does not know is one it could not have opened the session for.
736 known_identity(self, origin, &format!("session {:?}", token.0))?;
737 }
738 for publication in &self.publications {
739 let session = opened(self, &publication.session, "published")?;
740 named_branch(&publication.branch, "the published branch")?;
741 // A publication of some other branch than the one the session is on is
742 // the same kind of fiction, and the harder one to spot afterwards: the
743 // branch is what a journey asserts the publication was of.
744 if publication.branch != session.branch {
745 return Err(Error::Invalid {
746 reason: format!(
747 "the publication of session {:?} names branch {:?}, but that session is \
748 on {:?}",
749 publication.session.0, publication.branch, session.branch
750 ),
751 });
752 }
753 }
754 Ok(())
755 }
756
757 /// Every field an older readable document could hold means here what it meant
758 /// there, and the two the repository side gained in version 4 are absent from one
759 /// written before them — which is the answer, since that build held no hold and
760 /// counted no lines.
761 ///
762 /// Version 5's field is the exception, and it is carried rather than left at its
763 /// default: a document written before it *listed preserved work nobody had
764 /// published*, which is the `no` this build spells out. Left at the default it
765 /// would read as "nothing here can say", and a consumer's checked-in scenario
766 /// would start reporting work it had always called unpublished as work that may
767 /// have landed.
768 fn carry_forward(&mut self) {
769 if self.version < 5 {
770 for row in &mut self.preserved {
771 row.landed = Landed::No;
772 }
773 }
774 self.version = STATE_VERSION;
775 }
776}
777
778/// Refuse a record kept about a change request this state does not hold.
779fn opened_change(state: &HostState, id: &ChangeId, what: &str) -> Result<()> {
780 if state.changes.iter().any(|change| change.id == *id) {
781 return Ok(());
782 }
783 Err(Error::Invalid {
784 reason: format!(
785 "{what} is recorded for change request {:?}, but no change request by that \
786 identifier was opened",
787 id.0
788 ),
789 })
790}
791
792/// Refuse an identity key this provider was not seeded with.
793fn known_identity(state: &VcsState, origin: &str, what: &str) -> Result<()> {
794 if state
795 .identities
796 .iter()
797 .any(|identity| identity.origin == origin)
798 {
799 return Ok(());
800 }
801 Err(Error::Invalid {
802 reason: format!(
803 "{what} belongs to identity {origin:?}, which this provider does not know; {}",
804 known(state)
805 ),
806 })
807}
808
809/// A change request's title, refused when it names nothing.
810///
811/// The one thing a real host refuses about a title, and the only one this provider
812/// may: how long a title may be is the host's own rule rather than `onevcs`'s
813/// commit-subject rule, and a provider applying the stricter of the two would
814/// refuse what the host it stands in for accepts.
815pub(crate) fn titled(title: &str) -> Result<()> {
816 if title.trim().is_empty() {
817 return Err(Error::Invalid {
818 reason: "a change request's title is blank, so it names no change".to_owned(),
819 });
820 }
821 Ok(())
822}
823
824/// The session a token names, refused when this state does not hold one.
825fn opened<'a>(state: &'a VcsState, token: &SessionToken, what: &str) -> Result<&'a Session> {
826 if !events::is_safe_name(&token.0) {
827 return Err(Error::Invalid {
828 reason: format!("{:?} is not a session token", token.0),
829 });
830 }
831 session_of(state, token).ok_or_else(|| Error::Invalid {
832 reason: format!(
833 "session {:?} is {what} here, but no session by that token was opened",
834 token.0
835 ),
836 })
837}
838
839/// A seeded host side is refused if it holds a change nothing could address.
840impl Checked for HostState {
841 fn check(&self) -> Result<()> {
842 readable_version(self.version)?;
843 for change in &self.changes {
844 named_branch(&change.base, "the base of a seeded change request")?;
845 if change.id.0.is_empty() {
846 return Err(Error::Invalid {
847 reason: "a seeded change request carries no identifier".to_owned(),
848 });
849 }
850 // The commit a change request's checks are reported against is the whole
851 // evidence that a change reached anything, and the real implementation
852 // refuses a host answer that names none rather than passing a blank one
853 // through. A seeded one is refused for the same reason.
854 if change.head_sha.0.trim().is_empty() {
855 return Err(Error::Invalid {
856 reason: format!(
857 "the seeded change request {:?} names no commit its checks are \
858 reported against",
859 change.id.0
860 ),
861 });
862 }
863 }
864 // Both of these are recorded *about* a change request, by `open_change` and
865 // by nothing else, and both are read back by the id they are keyed under. An
866 // entry for a change nobody opened is one no call could ever reach, so it is
867 // refused rather than carried — unlike the checks, logs, and merge outcomes
868 // below it, which a journey deliberately seeds for a change it has not
869 // opened yet.
870 for (id, head) in &self.heads {
871 opened_change(self, id, "a head")?;
872 named_branch(head, "the head of a seeded change request")?;
873 }
874 for (id, title) in &self.titles {
875 opened_change(self, id, "a title")?;
876 // The real host refuses a title that names nothing, so a seeded one is
877 // refused for the same reason.
878 titled(title)?;
879 }
880 for id in self.bodies.keys() {
881 // Nothing is refused about the body itself: a host places no shape on
882 // prose, and a change request opened with an empty one is a scenario.
883 opened_change(self, id, "a body")?;
884 }
885 for (id, reason) in &self.drafts {
886 opened_change(self, id, "a draft reason")?;
887 // The publication rule the crate next door states, applied rather than
888 // restated: a seeded reason no publication could have carried is refused
889 // where the document is read, not answered from later.
890 reason.checked()?;
891 }
892 for id in &self.made_ready {
893 opened_change(self, id, "a lifted draft")?;
894 }
895 for id in &self.awaiting_checks {
896 opened_change(self, id, "a draft awaiting its checks")?;
897 }
898 for described in &self.described {
899 opened_change(self, &described.id, "a description")?;
900 // The real host refuses a title that names nothing, so a seeded one is
901 // refused for the same reason — and a body is prose, refused for nothing.
902 if let Some(title) = &described.title {
903 titled(title)?;
904 }
905 }
906 // A merge time is what `merge_time` answers and what a landing is recorded
907 // with, so a seeded one that is not a moment is refused here, where the
908 // document is read, rather than recorded as one.
909 for (id, at) in &self.merge_times {
910 if events::moment(at).is_none() {
911 return Err(Error::Invalid {
912 reason: format!(
913 "the merge time seeded for change request {:?} is {at:?}, which is \
914 not an RFC3339 moment",
915 id.0
916 ),
917 });
918 }
919 }
920 Ok(())
921 }
922
923 /// A version 2 document held no bodies, and a version 5 document's checks named
924 /// no commit; each reads as what it was — change requests opened with none, and
925 /// checks whose head that build never recorded. There is nothing to fill in — an
926 /// absent field is already that answer, and a check's commit is the one thing
927 /// that must never be inferred — so this is the version and nothing else. The one
928 /// carry a version 8 document needs, the `kind` its draft reasons lack, is done
929 /// where those are read (`drafts_of_any_version`), because it is a fact about
930 /// one value's shape rather than about the document.
931 fn carry_forward(&mut self) {
932 self.version = STATE_VERSION;
933 }
934}
935
936/// Refuse a document written at a version this build does not read.
937///
938/// Named rather than guessed at: a state whose shape is a later build's reads one
939/// way here and another way where that version is understood, and for a seeded
940/// scenario those two readings are two different tests. The refusal names the
941/// range as well as the version, because "too old" and "too new" are two different
942/// things to do about it — one is a document to re-seed, the other a build to
943/// update.
944fn readable_version(declared: u32) -> Result<()> {
945 if !(OLDEST_READABLE_VERSION..=STATE_VERSION).contains(&declared) {
946 return Err(Error::Invalid {
947 reason: format!(
948 "the document declares version {declared}; this build reads versions \
949 {OLDEST_READABLE_VERSION} to {STATE_VERSION}"
950 ),
951 });
952 }
953 Ok(())
954}