Align current CI source composition while retaining frozen scientific receivers
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 1/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, testing
Research direction
Start with devguide/pending_bugs/current_ci_source_composition.md and the linked exact source-context evidence; compare the old declared sources with the installed source origins and review the providers’ immutable metadata. The issue reports that the aligned context still exits at the HTTPS-only profile, with a supported route owned by uibcdf/molsyssuite#178. Done requires receiving that boundary and the listed hosted, native, clean-solve, minor-version, and platform gates; the issue says those gates remain unexecuted.
Written by the indexing model from the issue text.
Description
Current disposition — partial configuration delivery, 2026-11-09
Published 9375f3a8 ([skip ci]); exact source-context evidence, maintained report, combined receiving. Ordinary/current sources and explicit bootstrap floors are updated; original E4/fixed-candidate contexts and all matrices/triggers/scientific commands retain their identities. Complete administrative receiving passes101 tests/26 subtests and final local/fresh-export gates.
This issue remains partial/open. Actual old context exits1 for revision mismatch; aligned context still exits1 at the documented HTTPS-only profile on real SSH-origin installed clones. uibcdf/molsyssuite#178 owns an existing supported route or reviewed extension. No remote/config/shared metadata rewrite or synthetic pass; source-context receiving after that refusal and required hosted/native/clean-solve/minor/platform gates remain unexecuted. The separately passing1267-case private-wheel profiles do not clear this boundary.
Original request (preserved)
Current discrepancy and bounded objective
At DockingMT9a40e385d951b0521f6509de6b127083b78be61c, ordinary/full-matrix source declarations still select ArgDigest3d1ec53, MolSysMT00abb958 and Viewer78ede79. Actual recent editable receiving uses published ArgDigest07126411, MolSysMTefbe67e1 and Viewer1187fc18, with separately fingerprinted native bytes and support sources. These are different contexts; local editable PASS cannot receive the old hosted route or vice versa. MolSysMT's reviewed source metadata also adds Jinja2 and stronger bootstrap requirements.
Prepare the current ordinary CI/four-minor contexts with the exact already received sibling source commits and explicit compatible bootstrap dependencies. Preserve the original E4 manual receiver's sources/environment and the fixed0.1.0 candidate's immutable source contexts; independent current/historical routes must not be silently coupled. Keep existing matrices, workflow triggers/native scientific commands, optionality, public runtime bounds and required test scope intact. No automatic remote CI, source/native rebuild, package publication or sibling update.
Source/configuration acceptance
Demonstrate the old declared-vs-actual context discrepancy, review immutable old/new provider metadata and actual source origins, add meaningful guards for ordinary/current versus frozen-E4 binding and bootstrap requirements, then run complete affected administrative/source acquisition tests and actual shared installed-context preflight on routine3.14. Preserve all old outcomes/receipts and report declaration/installed-source receiving separately from a new clean Conda solve, every claimed interpreter/platform, native build or executed hosted CI. The latter remain broader #21/#28/#30/#47 evidence, not false PASS from a source pin update. Use the accepted shared SDK, preserve #31's bounded local acquisition variation/removal condition, update checkpoints and archive only this bounded configuration delivery when received.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/dockingmt
-
component:molsysmt component:peptidemt component:pharmacophoremt component:topomt needs-triage proposal
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
component:molsysmt component:peptidemt component:pharmacophoremt component:topomt needs-triage proposal
Difficulty 5/5 Over a week Newbie friendliness 24/100
-
component:molsysmt component:peptidemt needs-triage proposal
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
component:molsysmt component:peptidemt needs-triage proposal
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
component:molsysmt component:molsysviewer component:pytest-receptor partial proposal
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in uibcdf/dockingmt
Similar issues
-
area:core-platform effort:S priority:P3 risk:night-safe status:ready type:test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
randomparity/kdive#3620 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FinanceFlash/unvibecode#760 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
google-research/google-research#3470 ·
Maintainers usually reply within 21 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
mrvautin/ha-workouts#11 ·