
Is this host's baseline already current at the supplied upstream?
Source:R/lnk_baseline_current.R
lnk_baseline_current.RdPredicate helper for data-raw/snapshot_bcfp.sh and any other host-side
snapshot driver. Returns TRUE when this host's most recent snapshot row
already stamps the upstream build log carries, by its version and its
completion time — meaning the local snapshot is aligned with the bucket
and re-running would just churn.
Usage
lnk_baseline_current(
log,
host = .lnk_host(),
path = "data-raw/logs/bcfp_baselines.csv",
views = FALSE
)Arguments
- log
A list with
model_versionanddate_completed(the return oflnk_bucket_log()).- host
Host to scope the check by. Defaults to
.lnk_host()(LNK_HOST_ALIASwhere set, else the node name), the namelnk_baseline_append()writes rows under.- path
Path to the ledger CSV. Defaults to
data-raw/logs/bcfp_baselines.csvrelative to the working directory.- views
TRUEwhen the snapshot will load bcfishpass's reference views, so only a row that loaded them can make it current.
Value
TRUE when the latest counting row for host matches log's
version and completion time (the snapshot can be skipped). FALSE
otherwise — including when the ledger file is missing or has no counting
row for host.
Details
Per-host scoping is deliberate. Different hosts (M4, M1, cypher) each
populate their own local Postgres; one host stamping this week's SHA
must not gate the others. The predicate filters the ledger to rows
where host == <this host> before checking.
What counts (link#276, link#446). Only rows a snapshot wrote
(run_label starting snapshot-): a csv-sync- row loads nothing. With
views = TRUE (a snapshot asked for --with-bcfp-views), only snapshot
rows that loaded the views, so a newer views-less snapshot cannot skip a
reload of stale views. And the build must match by date_completed as
well as model_version: model_version is a code identity, so two weekly
builds of one commit share it (2026-08-18 and 2026-09-01 at
v0.7.15-47-ga702229), and a guard comparing only the version never
reloaded a host while the upstream rebuilt beneath it. A row whose date
cannot be read as an instant is not current.
"Latest row for host" means the row with the lexicographically greatest
run_started_pdt among the counting rows where host matches. The ledger's
run_started_pdt is written as YYYY-MM-DD HH:MM (PDT/PST), so
lexicographic ordering is also chronological ordering as long as the
format stays stable.
Examples
if (FALSE) { # \dontrun{
log <- lnk_bucket_log()
if (lnk_baseline_current(log)) {
message("This host already snapshotted at ", log$model_version,
"; skipping.")
quit(status = 0)
}
# ... otherwise proceed with the snapshot ...
} # }