Adopt distribution policy and qualify native ABI3 delivery
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system, devops, release
Research direction
Read devguide/pending_proposals/noarch_distribution_adoption.md and the referenced noarch_conda_workflow.md first, then inspect the delivered commits and administrative run records. Review the runtime environments, source routes, and public installation claims, and execute the component-owned installed scientific gate before promotion. Done means reviewed release evidence exists and no required candidate or installed evidence is missing, skipped, or failed.
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 — Adopt the governed noarch distribution policy under uibcdf/molsyssuite#45.
Delivered — Resource/publication controls e360e329ea3dc44f231fdb7611b133142439a9d4; optional shared fixed-Git/context adoption ba6428105107cd97481cb4f353c01d973f5a9190 through qualified SDK 2d32048457c6d37093ae509f5626d00a5cda121b (shared capability uibcdf/molsyssuite#107). Eighteen routes, thirteen fixed source records, two unchanged Git manifests and seven contexts are guarded. Nine archive/publication and seven source-route administrative tests pass. All 36 payload paths and eight installed-artifact cells/four required steps remain protected; original producer/file identity stays distinct from optional qualification SHA.
Measured — CI 37579435066 executes actual installed Git/context checks successfully on Linux Python 3.11–3.14 (five/five/six/seven pinned sources). Printed actual interpreter/version/repository/commit receipts and stable native source/run/attempt/step identities corroborate invocation. Policy 37579435796, Conda governance 37579435740 and separate current Viewer probe 37579435142 pass. Independent reporting/declaration/source/archive governance passes. Scientific source pins, existing test commands/triggers/recovery and moving-current Viewer workflow are preserved. Missing direct dependency/Python declarations are corrected without scientific minimum versions.
Remaining — Whole adoption and CI/recipe stay partial, publication access unknown. macOS source cells are queued/uncompleted at the recorded checkpoint; current native run must be checked before any platform/complete gate claim. Linux 3.11/3.12 still fail the known trajectory/CuPy test (one failure, 34 passes each) under this team's #14/#17 and LinDelINT #8. Administrative/source provenance checks do not clear scientific debt or authorize publication.
Environment helper controls are now delivered at 638354fad54e11eda93e92ddb26159619cb13c8f: metadata/context-derived six-file generator and checked Conda create/update share the accepted range proofs. Fourteen new guards plus the sixteen retained source/archive guards pass. Native policy 37582698174 and Conda governance 37582698222 pass exact-source verification; Reporting governance job 112665767155 in CI 37582697607 executes all helper/generation tests and generated-input checking successfully. The whole source CI run is not a successful gate: Linux 3.11 reproduces the known CuPy failure (one failure / 34 passes), and macOS jobs were queued at acquisition. The actual release plan is absent; only the example plan gains the new executed administrative step. Finish source-free production/development/docs actual invocations. Before release, commit a real reviewed plan, execute all exact-candidate gates including complete science and actual context checks, verify staging access, qualify one original file in eight installed cells with all four steps, promote those same bytes and independently verify public clean installation. Public Python admission remains #19. The illustrative 0.0.0 plan cannot authorize a release. No real build/staging/upload/replacement/promotion or installed scientific dispatch occurred.
Public observations — Conda/PyPI returned 404 and historical GitHub 0.1.0 had no assets on 2026-10-06. Those are bounded observations, not proof of historical absence or current installed compatibility. Documentation qualifies installation claims.
Owner record — devguide/pending_proposals/noarch_distribution_adoption.md
Central receipts — devguide/rollouts/elastnetmt_environment_controls_45_20261007.json (current helper checkpoint), devguide/rollouts/source_context_adoption_107_20261007.json and devguide/rollouts/elastnetmt_distribution_controls_45_20261006.json in uibcdf/molsyssuite
Historical implementation evidence af919eac0c7c5b522810eed565b0ff86a409cfe4 / 36902560182 and installed capability 7c3466a638167e5a5f46cc48a7aa95af66b77bc9 / 36908419767 retain their original bounded scopes; the current 36-file/eight-cell controls supersede their inventories. No registered historical bytes were changed.
- 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
crossplane/cli#432 ·
Maintainers usually reply within 3 days
-
Build: the CUDA backend fails without cuDNN instead of skipping the cuDNN shim (as the cuDF shim does)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
beehive-lab/TornadoVM#1248 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SimVascular/svZeroDSolver#253 ·
-
docs hermes medium
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Popoboxxo/ReqogniLoom#1353 ·
Maintainers usually reply within 1 day
-
difficulty: easy domain: devops effort: 1-4h enhancement good first issue smart-contracts Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Kaycee276/Chesster#469 · 2 comments ·
Maintainers usually reply within 1 day