Repository navigation
0.4.0: background process launch policy moves to zmqruntime (L3) - #20
Merged
Merged
Conversation
pyqt_reactive.process_launch is deleted; the policy is runtime machinery and lives in zmqruntime 0.6 (zmqruntime.process_launch). The log highlighter and system metrics sampler import it from there. Requires zmqruntime>=0.6,<0.7; CI validates against the zmqruntime 0.6.0 source candidate until it is published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lease check Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t admit from the installed runtime Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenHCS consolidation surface L3. 0.3.30 → 0.4.0 (breaking: a public module is removed).
pyqt_reactive.process_launchis deleted. The background-process launch policy is runtime machinery and now lives in zmqruntime 0.6 (zmqruntime.process_launch, 0.6.0: domain-blind vocabulary, declared messages, launch policy, execution transport config (L3) ZMQRuntime#28), where host families areBackgroundProcessPlatformsubclasses instead of enum members. The log highlighter and system-metrics sampler import it from there; their consumer tests stay here (tests/test_background_process_consumers.py), the policy's own tests moved with it.zmqruntime>=0.6,<0.7.requirements-ci.txtcarries it as a source candidate pinned to the exact PR commit (the same mechanism as the ObjectState candidate).test_release_dependency_declarationsnow requires any zmqruntime candidate to be pinned to a 40-hex commit, which keeps the resolver failure it was written for impossible. At release: publish zmqruntime 0.6.0 first, then drop the candidate line.Local:
pytest tests605 passed;scripts/check_ruff_added_lines.pyreports no diagnostics on added lines.Not merged or tagged; the owner releases.
L3 · pyqt-reactive PR · src −102 +3 · tests −102 +12
🤖 Generated with Claude Code