Align current CI source composition while retaining frozen scientific receivers

Abierto
  • ¿Algo no está bien?
#100 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
1/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
build-system, ci-cd, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug component:argdigest component:molsysmt component:molsysviewer

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.

Lenguaje dominante
Python
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de uibcdf/dockingmt

Todos los issues de uibcdf/dockingmt

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.