Complete contributor CI governance and skipped-push recovery
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with tests/test_ci_backlog.py, devtools/tests/test_ci_routes.py, and devguide/pending_bugs/full_ci_routes_and_skipped_push_recovery.md, then inspect the referenced GitHub Actions runs and the current CI configuration. Done means observing daily recovery and hosted external-PR enforcement, while keeping the documented scientific and platform follow-up work separate.
Written by the indexing model from the issue text.
Description
ElastNetMT independent receiving — 2026-10-09
Published main d26b6bc8299befb8c01b196eb1bbaf2e24759eee: actual daily 37950692582 executes its detector/reporting and attempts all eight Linux/macOS arm64 Python 3.11–3.14 scientific cells. All source-context/install/import/interpreter/architecture operations pass. Four 3.13/3.14 suites pass (both 3.14: 35 tests); four 3.11/3.12 suites retain 1 failed / 34 passed in the known test_anm_trajectory_generation CuPy case. The full run remains failed. The detector observes 69 skips / no eligible full watermark; probe 37795369442 preserves those facts while omitting tests. Actual daily observation is complete; no governance/probe/failed matrix clears debt. Scientific ownership stays uibcdf/elastnetmt#14 / uibcdf/lindelint#8.
Real open PR uibcdf/elastnetmt#22 by internal LMMV passes CI 37924781855, policy 37924782642, Conda controls 37924782553 and current-Viewer add-on 37924781852: 12 mandatory jobs, including eight full source/preflight cells (3.14: 71 passed) and separate add-on 19 passed. Requested head 6a3598a6 tests synthetic integration ed4aa4e620cb434e3ca9267ea905efbf0cbabf9a. This observes internal PR integration, not an external actor, main repair/debt clearance, merge or installed release. Its active branch is preserved.
Historical 37579435066 / 37582697607 now have completed macOS outcomes: 3.13/3.14 pass, 3.11/3.12 retain that same science failure. All eight source preflights pass; both whole workflows remain failed. Current main executable/helper/publication controls match qualified 638354fa; only four synchronized guides differ. Fresh protection retains 11 strict checks, explicit zero-approval PRs and administrator direct route; force/deletion remain disabled.
Central 75df841311cad5c021095f8abb5f2d0a735606a6 / immutable receiving receipt: six focused policy tests and offline governance pass. CI/distribution remain partial, platform claims unreviewed, access unknown; central CI totals remain 7 adopted / 8 partial. Source-free ordinary production/development/docs invocations, reviewed real release plan/exact successful candidate gates, original file/eight installed cells/same-byte promotion/normal public install and admission #19 remain separate owner work. No component edit, new science execution, environment solver, PR merge, pin/protection change or release/artifact operation. Pilot/enforcement unchanged.
Exact central governance 38002213705 is independently qualified. 447 original tests, publisher controls and retained XML pass in attempt 1. Coverage-only attempt 2 recovers the original upload storage AccessDenied location error, retaining the exact same coverage artifact ID/digest and inherited original governance timestamps. No tests were rerun by that recovery and no workflow/GPG/OIDC changes were made; upload success does not prove Codecov processing. The original failed upload remains visible.
Five independent global private-OpenCASTp access failures remain uibcdf/molsyssuite#102: environment 38002213712, component guides 38002213689 (16 other jobs pass), vendored guides 38002213658 (55 unavailable / 0 drift after interrupted clone), manifests 38002213743 (15 other jobs pass), labels 38002213671. This is bounded receiving/governance evidence, not whole-suite audit success.
This central receiving update preserves the owner record and issue state. The following implementation history predates these completed observations.
What — Complete ElastNetMT contributor CI governance and skipped-push recovery under uibcdf/molsyssuite#39. Status: partial, published directly to main through 9f47e1f (routing c68f662, collection correction 71f1179).
How — Main now explicitly requires PRs with zero mandatory approvals and nine strict checks: Reporting governance, policy / conformance (including Ruff), six supported Linux/macOS Python 3.11–3.13 scientific jobs and the existing specialized contract. dprada/LMMV retain observed administrator bypass; isandom retains maintain access and uses PR. No access role changed. Full unfiltered push/PR collection, minor-specific Conda environments, controlled suite revisions, the MolSysMT replacement limited to Python 3.13 and scientific pytest command stay intact. macOS is pinned to macos-15 with interpreter/arm64 assertions. Weekly Monday 09:00 UTC/manual complete execution and the unfiltered specialized contract remain available. Daily conditional recovery is staggered at 02:19 America/Mexico_City; history/API uncertainty or a failed decision job runs complete coverage.
Evidence — Eight administrative tests, three required standard-library reporting tests, Ruff over 59 files, indexes and central conformance pass locally. Initial governance probe https://github.com/uibcdf/elastnetmt/actions/runs/36775315293 at c68f662 retained five skips since executed full a47c067; record-head probe https://github.com/uibcdf/elastnetmt/actions/runs/36775593546 at 3d2c59b retained six. Policy runs 36775320115 and 36775602474 passed. Specialized contract https://github.com/uibcdf/elastnetmt/actions/runs/36775325575 passed its actual add-on verification at c68f662.
Local regression corrected — First manual CI https://github.com/uibcdf/elastnetmt/actions/runs/36775597556 failed older-minor collection because our new YAML administrative test imported PyYAML, absent from scientific Python 3.11/3.12 environments. This belongs to this implementation, not the old scientific/provider failure. Correction 71f1179 moves that guard to devtools/tests/test_ci_routes.py, explicitly selected by independent governance whose tools already include PyYAML. Scientific testpaths=["tests"], environments, sources, scientific assertions and command stay unchanged; no test is skipped. Corrected probe https://github.com/uibcdf/elastnetmt/actions/runs/36776675464 passed and retained seven skips; corrected policy 36776680458 passed. Final guard 9f47e1f also protects this administrative isolation.
Complete verification — Repeated complete CI https://github.com/uibcdf/elastnetmt/actions/runs/36776671299 at 71f1179 restored scientific collection. Both Python 3.13 jobs and Reporting governance passed; four older-minor actual scientific test steps failed. All six interpreter/arm64 assertions succeeded. Native logs on all four failing jobs confirm the known trajectory LinDelINT CuPy/auto-engine failure under uibcdf/elastnetmt#14 and uibcdf/lindelint#8; Linux 3.11 also shows all four backlog tests passed. GH Run Receptor preserved overall failure. Scientific code was not repaired or weakened.
Debt retained — Final probe https://github.com/uibcdf/elastnetmt/actions/runs/36777411290 at 9f47e1f passed actual reporting/CI guards and detector, retained eight skipped commits since older executed full a47c067, and omitted heavy jobs after complete CI failed. No failed or unexecuted complete coverage became a watermark. Final policy https://github.com/uibcdf/elastnetmt/actions/runs/36777416876 passed. Successful administrative probes did not erase debt.
Remaining — Observe actual daily recovery and hosted external-PR execution/enforcement; separately review installed-artifact/platform claims. Scientific receptor uniformity and component/provider integration remain under uibcdf/elastnetmt#14 and uibcdf/lindelint#8. Keep this issue open/partial.
Guards — tests/test_ci_backlog.py and devtools/tests/test_ci_routes.py. The original routing guard failed before implementation; the added isolation assertions protect the corrected collection mechanism.
Record — devguide/pending_bugs/full_ci_routes_and_skipped_push_recovery.md. Latest complete outcomes are retained here and in the central adoption record, preserving the final component source.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 3
- Avg merge
- 9h 40m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uibcdf/elastnetmt
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uibcdf/elastnetmt#13 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
uibcdf/elastnetmt#26 · 7 comments ·
-
proposal
Difficulty 4/5 3-5 days Newbie friendliness 12/100
uibcdf/elastnetmt#24 ·
-
component:ackredit
Difficulty 3/5 1-2 days Newbie friendliness 48/100
uibcdf/elastnetmt#20 · 10 comments ·
-
component:lindelint component:molsysmt component:molsysviewer enhancement partial
Difficulty 5/5 Over a week Newbie friendliness 30/100
uibcdf/elastnetmt#19 · 4 comments ·
All issues in uibcdf/elastnetmt
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
kubernetes-sigs/headlamp#7950 ·
Maintainers usually reply within 3 days
-
kind/bug
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
kubernetes-sigs/vsphere-csi-driver#4351 ·
Maintainers usually reply within 1 day
-
component/gpu-kubelet-plugin component/helm needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
kubernetes-sigs/dra-driver-nvidia-gpu#1559 ·
Maintainers usually reply within 1 day
-
OSCI'26
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
GauravKarakoti/SecureFlow#1301 ·
Maintainers usually reply within 1 day