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