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