homelab/stack
1
0
Fork 0
Code Issues 247 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

bcda: runout calendar in the checks and population labels on the Sync page #1298

New Issue
Closed
opened 2026-10-25 20:36:16 +00:00 by kert · 1 comment
kert commented 2026-10-25 20:36:16 +00:00
Owner
Copy Link

Upstream review docs/superpowers/specs/2026-10-25-bcda-upstream-review.md §F. Runout (Group/runout) is refreshed monthly through July of PY+1 and should be pulled with _since each month; after July no new runout data arrives.

  • check_since: runout_window warn after July of PY+1
  • Sync page labels current vs runout watermarks and ledger rows
Upstream review docs/superpowers/specs/2026-10-25-bcda-upstream-review.md §F. Runout (`Group/runout`) is refreshed monthly through July of PY+1 and should be pulled with `_since` each month; after July no new runout data arrives. - [ ] `check_since`: `runout_window` warn after July of PY+1 - [ ] Sync page labels `current` vs `runout` watermarks and ledger rows
kert added this to the P52: BCDA v3 migration — client, crosswalk-driven flatteners, vendored upstream fixtures, proving notebook milestone 2026-10-25 20:36:16 +00:00
kert added the clidocs labels 2026-10-25 20:36:16 +00:00
kert commented 2026-10-25 21:11:48 +00:00
Author
Owner
Copy Link

Done in 2cc1300: runout_window warn after July of PY+1; population column on the Sync page ledger and in sync status watermarks.

Done in 2cc1300: `runout_window` warn after July of PY+1; `population` column on the Sync page ledger and in `sync status` watermarks.
kert closed this issue 2026-10-25 21:11:49 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label cli docs
Milestone
No items
No Milestone P52: BCDA v3 migration — client, crosswalk-driven flatteners, vendored upstream fixtures, proving notebook
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#1298
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?