Repository navigation
Require ezmsg 3.10.0b5, ezmsg-baseproc 1.15.0 and ezmsg-sigproc 3.10.0 - #12
Merged
Merged
Conversation
- `ezmsg-baseproc>=1.15.0`: its hash witness no longer holds the first message's axes, which pinned cross-process shared memory and killed the subscriber's channel when the publisher grew it (ezmsg-org/ezmsg#272, ezmsg-org/ezmsg-baseproc#17). 1.15.0 itself requires ezmsg 3.10.0b5. - `ezmsg>=3.10.0b5`: SHM hardening (#272), coordinate-axis elision across processes, and fingerprints computed when pickling. Note that SHM-delivered messages are now read-only; a scan found no in-place writes to received data in this repo. - `ezmsg-sigproc>=3.10.0` (was `>=2.23.0`): sigproc 3.8.x–3.9.x import `resolve_chunk_dim`, renamed in baseproc 1.14, so the old floor allowed a combination that fails to import. Tested locally against ezmsg 3.10.0b5 + ezmsg-baseproc 1.15.0 from PyPI and ezmsg-sigproc 3.11.0: 161 passed. (`tests/integration/test_dnss_system.py::test_dnss_synth` fails with a component address collision only when another GraphServer is already listening on the default port.)
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
1 participant
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.
ezmsg-baseproc>=1.15.0: its hash witness no longer holds the first message's axes, which pinned cross-process shared memory and killed the subscriber's channel when the publisher grew it (Cross-process SHM grow kills the subscriber channel (BufferError) when a received message is still referenced ezmsg#272, Hash witness retains the first message's axes, pinning cross-process SHM (causes ezmsg#272) ezmsg-baseproc#17). 1.15.0 itself requires ezmsg 3.10.0b5.ezmsg>=3.10.0b5: SHM hardening (#272), coordinate-axis elision across processes, and fingerprints computed when pickling. Note that SHM-delivered messages are now read-only; a scan found no in-place writes to received data in this repo.ezmsg-sigproc>=3.10.0(was>=2.23.0): sigproc 3.8.x–3.9.x importresolve_chunk_dim, renamed in baseproc 1.14, so the old floor allowed a combination that fails to import.Tested locally against ezmsg 3.10.0b5 + ezmsg-baseproc 1.15.0 from PyPI and ezmsg-sigproc 3.11.0: 161 passed. (
tests/integration/test_dnss_system.py::test_dnss_synthfails with a component address collision only when another GraphServer is already listening on the default port.)