Repository navigation
Conversation
Normal RegistryService readiness prepares the authoritative schema source closure. Remove the deleted UnifiedParameterInfo reexport and pin PythonIntrospect 0.2.0/ObjectState 1.3.0 candidates; availability and integrated receiving remain pending. Fixes #726
…claration-presentation-consumer-20261004
…claration-presentation-consumer-20261004
…claration-presentation-consumer-20261004
…claration-presentation-consumer-20261004
…claration-presentation-consumer-20261004
|
Future whole-main receiving17 is pinned at772971bf (merged522/727 and828/836 guidance). The existing receiving16/fresh scientists remain unchanged. This machine cannot reuse the private-wheel receipt paths under ~/.local/state/openhcs-maintenance from the other machine: those paths are absent here. Official python-introspect0.2.0 and ObjectState1.3.0 version endpoints currently return404. Original trusted publishers37343520504 (PI43cdbf3) and37343598071 (OS7db1519) are queued, not failed or retried. Root remains the original dependency release owner. Please hand off the exact retained, qualified release wheels plus SHA/source manifest through the existing artifact route so normal offline receiving need not duplicate their builds or wait on hosted publication capacity. I own OpenHCS bundle integration, not a competing publisher/tag/version change. No lower floors, shared install, current SCI overlay or new environment. The unchanged accepted16 baseline has already restored three fresh authors; this concrete artifact boundary affects only the NEXT whole bundle. |
|
Determining update for future receiving17: merged845 d5f6600 is now queued into the next ordinary guidance revision; build01/772971bf remains preserved, not relabeled or overlaid. The same current-main diff includes0eacae5b7 and now requires PI>=0.2.1, OS>=1.3.1, ZMQRuntime>=0.4.1. Original publisher runs37354415119/37347980512/37354419708 remain queued. Root remains the original release/artifact owner: please hand off the retained qualified three release wheels and SHA/source manifests through the existing route. Main declares PI83c1efe/OS c75a457/ZMQ29e2a86; OS existing1.3.1 tag run is1d36774, so the actual retained-wheel provenance needs the original owner reconciliation, not an unverified receiver claim. No competing dependency build, publisher retry, tag change or shared install. Existing16 authors continue unchanged. |
|
Concrete artifact progress, not another publisher wait: original GitHub releases now supply PI0.2.1 and ZMQRuntime0.4.1. Downloaded into receiving17/dependency-artifacts02; release SHA, ZIP CRC, every hashed RECORD member and metadata version pass. Annotated tags resolve exactly83c1efe5/29e2a869 as main declares. Their queued Actions/PyPI404 do not block these original qualified wheels. ObjectState1.3.1 is the only remaining binary: original release endpoint404, run37347980512 queued. Root, please provide the retained qualified OS wheel+SHA/source manifest via the same release/artifact route, including declaredc75a457 versus existingtag1d36774 reconciliation. No duplicate rebuild/upload/shared install. Built17 revision01 and active science15/16 remain unchanged; next ordinary revision includes845. |
Headless saved configuration admission currently builds editor help and copied parameter metadata before compilation. Use PythonIntrospect's canonical ParameterInfo declaration and ObjectState's declaration-owned help/reset views. Normal registry preparation warms the registered dataclass source closure before READY, retaining constructor/factory and live-value semantics. Remove the obsolete UnifiedParameterInfo reexport.
Pin merged PythonIntrospect 43cdbf3 and ObjectState 7db1519; update their supported version floors to 0.2.0 and 1.3.0. Their source changes are already merged in PI12 and OS22.
Validation: the coherent release wheels are installed through pip in the shared environment, actual module/distribution origins and payloads match the merged dependency sources, pip check passes, and the OpenHCS native build preserved all four qualified ABI payloads. The production-default Illum3 observation passed full declared nonempty image parity against both retained native output sets at the existing tolerance (maximum pixel difference 2.98e-8). Recorded compile/execution/client total: 206.535/264.932/565.896 ms. Native execution mean 626.957 ms gives 2.366x execution speedup; native full invocation mean 695.522 ms gives 1.229x total. These older unpaired observations do not establish a current corpus-wide minimum or an individual-patch gain. Startup and kernel preparation are outside pipeline clocks.
Earlier first-job saved admission improved 129.320 to 82.766 ms; the already-warm 3D control showed no improvement. Both limits remain recorded in the committed evidence. Current head ae8 includes the merged catalog startup changes and local qualification; the final manuscript suite will run from merged main with the latest merged dependency updates.
The v0.2.0/v1.3.0 release publishers remain queued, so public PyPI availability is not yet established. Local qualification uses verified source-built release wheels. Merge is authorized under the user's instruction to merge locally qualified changes and handle main CI separately. The pre-existing Python 3.10 recursive decoder defect remains tracked independently in PI13.
Closes #726