Release 2.1.1 with CI/CD upgrades and infrastructure improvements#528
Merged
reactive-firewall merged 183 commits intostablefrom Mar 4, 2026
Merged
Release 2.1.1 with CI/CD upgrades and infrastructure improvements#528reactive-firewall merged 183 commits intostablefrom
reactive-firewall merged 183 commits intostablefrom
Conversation
Changes in file .github/workflows/CD-PyPi.yml: ensure shell is running bash
Changes in file .github/workflows/CD-PyPi.yml: * Flushed out more like working CI-Build for builds Changes in file docs/conf.py: * version bump to 2.1 series Changes in file multicast/__init__.py: * version bump to 2.1 series Changes in file pyproject.toml: * version bump to 2.1 series
Changes in file multicast/__main__.py: * marked branch as defensive code Changes in file multicast/hear.py: * tweaked the doctests slightly Changes in file tests/test_hear_server_activate.py: * added a few more tests
Changes in file .github/tools/fetch-test-reporter: * version bump
Changes in file docs/conf.py: * version bump Changes in file multicast/__init__.py: * version bump Changes in file pyproject.toml: * version bump
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.29.2 to 3.29.3. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@181d5ee...d6bbdef) --- updated-dependencies: - dependency-name: github/codeql-action dependency-version: 3.29.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Changes in file .github/workflows/codeql-analysis.yml: * version bump to CodeQL v3.29.3 Changes in file .github/workflows/scorecard.yml: * version bump to CodeQL v3.29.3
Changes in file .github/workflows/CI-BUILD.yml: * Added new concurancy group settings Changes in file .github/workflows/CI-CHGLOG.yml: * Added new concurancy group settings Changes in file .github/workflows/CI-DOCS.yml: * Added new concurancy group settings Changes in file .github/workflows/CI-MATs.yml: * Added new concurancy group settings Changes in file .github/workflows/Tests.yml: * Added new concurancy group settings * Added throttling limits Changes in file .github/workflows/bandit.yml: * Added new concurancy group settings Changes in file .github/workflows/codeql-analysis.yml: * Added new concurancy group settings Changes in file .github/workflows/flake8.yml: * Added new concurancy group settings Changes in file .github/workflows/makefile-lint.yml: * Added new concurancy group settings Changes in file .github/workflows/markdown-lint.yml: * Added new concurancy group settings Changes in file .github/workflows/scorecard.yml: * Added new concurancy group settings Changes in file .github/workflows/shellcheck.yml: * Added new concurancy group settings Changes in file .github/workflows/yaml-lint.yml: * Added new concurancy group settings
Changes in file .github/workflows/CI-BUILD.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/CI-CHGLOG.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/CI-DOCS.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/CI-MATs.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/Tests.yml: * Removed limits (kept throttling) Changes in file .github/workflows/bandit.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/codeql-analysis.yml: * Retuned limit for schedule runs Changes in file .github/workflows/flake8.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/makefile-lint.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/markdown-lint.yml: * Removed limits reverting to previous LGV Changes in file .github/workflows/scorecard.yml: * Retuned limit for schedule runs Changes in file .github/workflows/shellcheck.yml: * Removed limits reverting to previous LGV
Bumps [reactive-firewall/flake8-cq](https://github.com/reactive-firewall/flake8-cq) from 1.5 to 1.6. - [Release notes](https://github.com/reactive-firewall/flake8-cq/releases) - [Commits](reactive-firewall/flake8-cq@33e74e4...ec38e8f) --- updated-dependencies: - dependency-name: reactive-firewall/flake8-cq dependency-version: '1.6' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.29.3 to 3.29.5. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@d6bbdef...51f7732) --- updated-dependencies: - dependency-name: github/codeql-action dependency-version: 3.29.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Changes in file .github/workflows/codeql-analysis.yml: * version bump CodeQL Changes in file .github/workflows/flake8.yml: * version bump flake8-cq Changes in file .github/workflows/scorecard.yml: * version bump CodeQL
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.29.7 to 3.29.8. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@51f7732...76621b6) --- updated-dependencies: - dependency-name: github/codeql-action dependency-version: 3.29.8 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [reactive-firewall/flake8-cq](https://github.com/reactive-firewall/flake8-cq) from 1.6 to 2.1. - [Release notes](https://github.com/reactive-firewall/flake8-cq/releases) - [Commits](reactive-firewall/flake8-cq@ec38e8f...4814c66) --- updated-dependencies: - dependency-name: reactive-firewall/flake8-cq dependency-version: '2.1' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/cache](https://github.com/actions/cache) from 4.2.3 to 4.2.4. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@5a3ec84...0400d5f) --- updated-dependencies: - dependency-name: actions/cache dependency-version: 4.2.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4.3.0 to 5.0.0. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@d3f86a1...634f93c) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.2 to 5.0.0. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@11bd719...08c6903) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Changes in file .github/actions/checkout-and-rebuild/action.yml: * Version bump actions/checkout to v5.0.0 Changes in file .github/workflows/codeql-analysis.yml: * Harden use of actions/checkout by dropping credentials when done.
Changes in file .github/actions/checkout-and-rebuild/action.yml: * Version bump actions/download-artifact to v5
Changes in file .github/actions/checkout-and-rebuild/action.yml: * version bumps Changes in file .github/workflows/CD-PyPi.yml: * version bumps Changes in file .github/workflows/CI-BUILD.yml: * version bumps Changes in file .github/workflows/CI-CHGLOG.yml: * version bumps Changes in file .github/workflows/CI-DOCS.yml: * version bumps Changes in file .github/workflows/CI-MATs.yml: * version bumps Changes in file .github/workflows/Tests.yml: * version bumps Changes in file .github/workflows/bandit.yml: * version bumps Changes in file .github/workflows/codeql-analysis.yml: * version bumps Changes in file .github/workflows/flake8.yml: * version bumps Changes in file .github/workflows/makefile-lint.yml: * version bumps Changes in file .github/workflows/markdown-lint.yml: * version bumps Changes in file .github/workflows/scorecard.yml: * version bumps Changes in file .github/workflows/shellcheck.yml: * version bumps Changes in file .github/workflows/yaml-lint.yml: * version bumps
Changes in file .github/workflows/CI-CHGLOG.yml: * hotfix for regression of download-artifacts action logic after version bump
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 5.4.3 to 5.5.0. - [Release notes](https://github.com/codecov/codecov-action/releases) - [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md) - [Commits](codecov/codecov-action@18283e0...fdcc847) --- updated-dependencies: - dependency-name: codecov/codecov-action dependency-version: 5.5.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.29.8 to 3.29.11. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@76621b6...3c3833e) --- updated-dependencies: - dependency-name: github/codeql-action dependency-version: 3.29.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Changes in file .github/workflows/makefile-lint.yml: * added need for setup-go for checkmake
Changes in file .github/workflows/Tests.yml: * version bumps Changes in file .github/workflows/codeql-analysis.yml: * version bumps Changes in file .github/workflows/makefile-lint.yml: * version bumps Changes in file .github/workflows/scorecard.yml: * version bumps
Changes in file .github/actions/test-reporter-upload/action.yml: * version bump to new version like workflows
Bumps [actions/attest-build-provenance](https://github.com/actions/attest-build-provenance) from 2.4.0 to 3.0.0. - [Release notes](https://github.com/actions/attest-build-provenance/releases) - [Changelog](https://github.com/actions/attest-build-provenance/blob/main/RELEASE.md) - [Commits](actions/attest-build-provenance@e8998f9...977bb37) --- updated-dependencies: - dependency-name: actions/attest-build-provenance dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/labeler](https://github.com/actions/labeler) from 5.0.0 to 6.0.1. - [Release notes](https://github.com/actions/labeler/releases) - [Commits](actions/labeler@8558fd7...634933e) --- updated-dependencies: - dependency-name: actions/labeler dependency-version: 6.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.6.0 to 6.0.0. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@a26af69...e797f83) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
* These changes are part of the review of PR #528 Changes in file README.md: * Slightly improved badges by adding links
…deCov * This change fixes a regression found when reviewing PR #528 Changes in file .github/workflows/Tests.yml: * fix input key for codecov test uploads
* These changes are related to the review of PR #528 Changes in file tests/test_build.py: * Resolve PYL-E0601 Changes in file tests/test_deps.py: * Resolve PYL-E0601 Changes in file tests/test_manifest.py: * Resolve PYL-E0601
* This style change is related to the review of PR #528 Changes in file tests/test_hear_server_activate.py: * add suppression comment to `pass` statement to resolve false PYL-W0107 flagging of a test fixture.
* These changes relate to review of PR #528 Changes in file tests/test_build.py: * resolve PY-D0002 by adding class docstrings Changes in file tests/test_hear_server.py: * resolve PY-D0002 by adding class docstrings Changes in file tests/test_manifest.py: * resolve PY-D0002 by adding class docstrings
* These changes are related to review of PR #528 Changes in file tests/profiling.py: * Added some trivial docstrings to test code to resolve some PY-D0003 * Suppressed some PY-D0003 to reduce noise for performance test code linting. * Related changes
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tests/profiling.py (1)
233-255: 🛠️ Refactor suggestion | 🟠 MajorAdd short docstrings to nested wrappers instead of suppressing PY-D0003.
At Line 233, Line 234, Line 253, and Line 254, the nested functions are still undocumented and currently rely on
skipcq: PY-D0003. Please add concise CEP-7-style docstrings and drop those suppressions.Suggested patch
- def inner(func): # skipcq: PY-D0003 - def profiled_func(*args, **kwargs): # skipcq: PY-D0003 + def inner(func): + """Wrap and return a line-profiled callable.""" + def profiled_func(*args, **kwargs): + """Execute `func` under LineProfiler and print collected stats.""" try: profiler = LineProfiler() profiler.add_function(func) @@ - def inner(func): # skipcq: PY-D0003 - def nothing(*args, **kwargs): # skipcq: PY-D0003 + def inner(func): + """Return a no-op profiling wrapper when LineProfiler is unavailable.""" + def nothing(*args, **kwargs): + """Execute and return `func` unchanged.""" return func(*args, **kwargs)Reference: https://peps.python.org/pep-0257/
As per coding guidelines, "undocumented function definitions and class definitions in the project's Python code are assumed incomplete" and docstrings should align with CEP-7.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/profiling.py` around lines 233 - 255, The nested wrapper functions lack docstrings and currently use skipcq: PY-D0003; update the nested functions inner, profiled_func (inside do_profile when LineProfiler is available) and inner, nothing (inside the ImportError fallback) to include concise CEP-7/PEP-257 style one-line docstrings describing their role (e.g., "Wraps and profiles the wrapped function" and "Pass-through wrapper for non-profiling mode"), then remove the skipcq: PY-D0003 suppressions for those definitions so they are documented according to project guidelines.
♻️ Duplicate comments (5)
tests/test_manifest.py (1)
124-128:⚠️ Potential issue | 🟠 MajorMove assertion outside the
finallyblock.The assertion on line 128 is inside the
finallyblock. WhiletheBuildtxtis correctly initialized toNonebefore the try (avoidingUnboundLocalError), placing assertions infinallyblocks is problematic:
finallyblocks are for cleanup logic only- If
checkPythonCommandraises an exception, this assertion will also fail (sincetheBuildtxtremainsNone), and theAssertionErrorwill mask the original exception📝 Proposed fix
try: theBuildtxt = context.checkPythonCommand(build_arguments, stderr=subprocess.STDOUT) finally: os.umask(original_umask) # Restore the original umask - self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed state") + self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed state")🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/test_manifest.py` around lines 124 - 128, The assertion on theBuildtxt is inside the finally block which should be reserved for cleanup (restoring original_umask); move the self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed state") out of the finally and place it immediately after the try/finally so any exception from context.checkPythonCommand is not masked; keep the os.umask(original_umask) call inside the finally and ensure theBuildtxt variable (initialized to None before the try) is used in the post-finally assertion.tests/test_build.py (1)
107-111:⚠️ Potential issue | 🟠 MajorMove assertion outside the
finallyblock.Same issue as in
tests/test_manifest.py: the assertion on line 111 is inside thefinallyblock. WhiletheBuildtxtis correctly initialized toNonebefore the try (avoidingUnboundLocalError), placing assertions infinallyblocks masks original exceptions when the command fails.📝 Proposed fix
try: theBuildtxt = context.checkPythonCommand(build_arguments, stderr=subprocess.STDOUT) finally: os.umask(original_umask) # Restore the original umask - self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed state") + self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed state")🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/test_build.py` around lines 107 - 111, The assertion for theBuildtxt is currently inside the finally block which masks original exceptions; move the self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed state") out of the finally and place it immediately after the try/finally completes (i.e., after restoring os.umask) so that the try block runs context.checkPythonCommand(build_arguments, stderr=subprocess.STDOUT) and any exceptions from that call are preserved; keep the os.umask(original_umask) call inside the finally to ensure cleanup, and reference theBuildtxt, build_arguments, context.checkPythonCommand and original_umask when making the change.tests/test_hear_server_activate.py (2)
147-150:⚠️ Potential issue | 🟡 MinorRegister cleanup immediately after server creation to avoid leak-on-assertion paths.
At Line 147, Line 162, Line 176, and Line 184,
server_close()is only reached if assertions pass. If an assertion fails first, sockets remain open in the test process.Reference: https://docs.python.org/3/library/unittest.html#unittest.TestCase.addCleanup
🔧 Suggested fix
def test_initialization_with_valid_address(self): ... server = multicast.hear.McastServer(('224.0.0.1', self._the_test_port), None) + self.addCleanup(server.server_close) self.assertIsInstance(server, multicast.hear.McastServer) self.assertIsInstance(server, socketserver.UDPServer) - server.server_close() # Clean up def test_initialization_with_logger_name(self): ... server = multicast.hear.McastServer(test_addr, None) + self.addCleanup(server.server_close) self.assertIsNotNone(server.logger) self.assertTrue(server.logger.name.endswith('239.0.0.9')) - server.server_close() # Clean up def test_initialization_without_address(self): ... server = multicast.hear.McastServer(None, None) + self.addCleanup(server.server_close) self.assertIsNotNone(server.logger) ... - server.server_close() # Clean up server = multicast.hear.McastServer((), None) + self.addCleanup(server.server_close) self.assertIsNotNone(server.logger) ... - server.server_close() # Clean upAlso applies to: 162-166, 176-190
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/test_hear_server_activate.py` around lines 147 - 150, After creating the McastServer instance (multicast.hear.McastServer in the test), immediately register a cleanup with the test harness (use self.addCleanup(server.server_close)) so the socket is always closed even if subsequent assertions fail; do this right after server = multicast.hear.McastServer(...) in the test methods that currently call server.server_close() at the end (replace or keep the final explicit close but ensure addCleanup is added immediately after creation).
164-164:⚠️ Potential issue | 🟠 MajorLogger-name assertions are overly platform-specific and can fail on Windows CI.
At Line 164 and Lines 178-189, strict suffix/equality checks assume resolved bind address behavior that is not stable across OS socket stacks. This makes the tests portability-fragile.
Reference:
- Python socket docs: https://docs.python.org/3/library/socket.html
- Python socketserver docs: https://docs.python.org/3/library/socketserver.html
🔧 Suggested fix (portable assertion pattern)
- self.assertTrue(server.logger.name.endswith('239.0.0.9')) + self.assertTrue( + server.logger.name.startswith("multicast.hear.McastServer."), + f"Unexpected logger name: {server.logger.name}", + ) ... - self.assertEqual( - server.logger.name, - f"multicast.hear.McastServer.{multicast._MCAST_DEFAULT_GROUP}" - ) + self.assertTrue( + server.logger.name.startswith("multicast.hear.McastServer."), + f"Unexpected logger name: {server.logger.name}", + ) ... - self.assertEqual( - server.logger.name, - f"multicast.hear.McastServer.{multicast._MCAST_DEFAULT_GROUP}" - ) + self.assertTrue( + server.logger.name.startswith("multicast.hear.McastServer."), + f"Unexpected logger name: {server.logger.name}", + )#!/bin/bash # Verify this portability risk is reachable in current repo state. # 1) Confirm Windows is part of CI matrix. rg -n "windows-latest|windows" .github/workflows -g "*.yml" -C2 # 2) Confirm strict logger assertions are present in this test file. rg -n "logger\.name\.endswith\('239\.0\.0\.9'\)|logger\.name,\s*$|_MCAST_DEFAULT_GROUP" tests/test_hear_server_activate.py -C2 # 3) Inspect logger derivation/bind flow in server implementation. rg -n "def _sync_logger|def server_bind|getsockname|server_address" multicast/hear.py -C4As per coding guidelines, "Prioritize portability over clarity, especially when dealing with cross-Python compatibility."
Also applies to: 178-189
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/test_hear_server_activate.py` at line 164, The test's strict logger-name checks are platform-fragile; update the assertions in tests/test_hear_server_activate.py to use a portable pattern (e.g., check that server.logger.name contains or matches the multicast group string rather than equals/endswith) — replace assertions like server.logger.name.endswith('239.0.0.9') and any exact-equality checks with a containment or regex match against _MCAST_DEFAULT_GROUP (or the literal "239.0.0.9"), or alternatively assert that server.server_address / server.socket.getsockname() reports the expected multicast group, so the tests tolerate OS-specific logger name formatting..github/workflows/Tests.yml (1)
848-848:⚠️ Potential issue | 🟠 MajorMatrix job output is still non-deterministic across legs.
Line 848 still maps a matrix-job output (
integration_upload_artifact_outcome) from a shared output key. In matrix jobs, reused output keys can be overwritten by the last finishing leg, so this value is not reliably representative.Reference: https://docs.github.com/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idoutputs
In GitHub Actions matrix jobs, when `jobs.<job_id>.outputs` uses the same output name for every matrix leg, which leg’s value is retained and what is the recommended way to aggregate per-leg outcomes?🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/Tests.yml at line 848, The workflow maps a matrix-job output into a single shared key (integration_upload_artifact_outcome) so the last-finishing matrix leg overwrites the value; change each matrix leg to emit a uniquely-named output (e.g., integration_upload_artifact_outcome_${{ matrix.<id> }}) from the step producing outcome (steps.integration-reports-upload.outcome) and then add an aggregator job that reads all per-leg outputs via needs.<matrix_job>.outputs to deterministically collect/aggregate results; update any consumers to reference the aggregated output instead of the single shared key.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/Tests.yml:
- Line 130: The workflow uses the incorrect credential input name for the
actions/checkout step: replace the unsupported "github-token" input with the
documented "token" input for the checkout action (update the step that currently
sets github-token: ${{ env.GH_TOKEN }} to use token: ${{ env.GH_TOKEN }});
search for any other occurrences of "github-token" in the workflow and rename
them to "token" so actions/checkout receives the intended credential.
In `@README.md`:
- Line 31: The badge anchor in README.md currently links to the repository
homepage; update the anchor href around the OSSF-Scorecard badge markdown so it
points to the OSSF Scorecard viewer for this repo instead (replace the current
https://github.com/reactive-firewall-org/multicast URL with the OSSF Scorecard
viewer URL for reactive-firewall-org/multicast), keeping the existing image
alt/text and badge image URL unchanged.
---
Outside diff comments:
In `@tests/profiling.py`:
- Around line 233-255: The nested wrapper functions lack docstrings and
currently use skipcq: PY-D0003; update the nested functions inner, profiled_func
(inside do_profile when LineProfiler is available) and inner, nothing (inside
the ImportError fallback) to include concise CEP-7/PEP-257 style one-line
docstrings describing their role (e.g., "Wraps and profiles the wrapped
function" and "Pass-through wrapper for non-profiling mode"), then remove the
skipcq: PY-D0003 suppressions for those definitions so they are documented
according to project guidelines.
---
Duplicate comments:
In @.github/workflows/Tests.yml:
- Line 848: The workflow maps a matrix-job output into a single shared key
(integration_upload_artifact_outcome) so the last-finishing matrix leg
overwrites the value; change each matrix leg to emit a uniquely-named output
(e.g., integration_upload_artifact_outcome_${{ matrix.<id> }}) from the step
producing outcome (steps.integration-reports-upload.outcome) and then add an
aggregator job that reads all per-leg outputs via needs.<matrix_job>.outputs to
deterministically collect/aggregate results; update any consumers to reference
the aggregated output instead of the single shared key.
In `@tests/test_build.py`:
- Around line 107-111: The assertion for theBuildtxt is currently inside the
finally block which masks original exceptions; move the
self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed
state") out of the finally and place it immediately after the try/finally
completes (i.e., after restoring os.umask) so that the try block runs
context.checkPythonCommand(build_arguments, stderr=subprocess.STDOUT) and any
exceptions from that call are preserved; keep the os.umask(original_umask) call
inside the finally to ensure cleanup, and reference theBuildtxt,
build_arguments, context.checkPythonCommand and original_umask when making the
change.
In `@tests/test_hear_server_activate.py`:
- Around line 147-150: After creating the McastServer instance
(multicast.hear.McastServer in the test), immediately register a cleanup with
the test harness (use self.addCleanup(server.server_close)) so the socket is
always closed even if subsequent assertions fail; do this right after server =
multicast.hear.McastServer(...) in the test methods that currently call
server.server_close() at the end (replace or keep the final explicit close but
ensure addCleanup is added immediately after creation).
- Line 164: The test's strict logger-name checks are platform-fragile; update
the assertions in tests/test_hear_server_activate.py to use a portable pattern
(e.g., check that server.logger.name contains or matches the multicast group
string rather than equals/endswith) — replace assertions like
server.logger.name.endswith('239.0.0.9') and any exact-equality checks with a
containment or regex match against _MCAST_DEFAULT_GROUP (or the literal
"239.0.0.9"), or alternatively assert that server.server_address /
server.socket.getsockname() reports the expected multicast group, so the tests
tolerate OS-specific logger name formatting.
In `@tests/test_manifest.py`:
- Around line 124-128: The assertion on theBuildtxt is inside the finally block
which should be reserved for cleanup (restoring original_umask); move the
self.assertIsNotNone(theBuildtxt, f"Failed with {build_arguments} in relaxed
state") out of the finally and place it immediately after the try/finally so any
exception from context.checkPythonCommand is not masked; keep the
os.umask(original_umask) call inside the finally and ensure theBuildtxt variable
(initialized to None before the try) is used in the post-finally assertion.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to data retention organization setting
📒 Files selected for processing (8)
.github/workflows/Tests.ymlREADME.mdtests/profiling.pytests/test_build.pytests/test_deps.pytests/test_hear_server.pytests/test_hear_server_activate.pytests/test_manifest.py
* These changes are part of the review of PR #528 Changes in file multicast/hear.py: * fixed grammar in docstring Changes in file multicast/recv.py: * fixed grammar in docstring Changes in file tests/test_hear_server_activate.py: * improved testing of hear server initialization/cleanup for edge-cases.
* This change is part of the review of PR #528 Changes in file tests/test_hear_server_activate.py: * de/re-indented for style
* These changes are part of the review of PR #528 Changes in file .github/workflows/CI-MATs.yml: * refactored commit link format Changes in file .github/workflows/Tests.yml: * improved report logic for non-pytest formatting slightly * refactored commit link format
Changes in file .github/workflows/Tests.yml: * corrected input key for checkout action
* This change is related to review of PR #528 Changes in file README.md: * added badge link for scorecard
* These changes are part of the review of PR #528 * These changes are related to work on GHI #527 Changes in file .github/actions/check-control/action.yml: * Refactored variables in CI/CD and traded risks of input-injection (which was minor) for risk of data-leak (which is trivial and N/A in public repo)
* These changes are part of the review of PR #528 * These changes resolve regressions from GHI #362 * These changes also relate to GHI #441 * These changes also impact GHI #380 Changes in file .codecov.yml: * Refactored statuses again Changes in file .coveragerc: * Updated config with modern options * Adjusted scope of reports slighly * Related changes Changes in file Makefile: * Version bumped (still targeting python3.9+) * Related changes Changes in file docs/requirements.txt: * Version bumped related documentation extras Changes in file pyproject.toml: * Related changes Changes in file requirements.txt: * Version bumped (still targeting python3.9+) Changes in file tests/check_coverage_helper: * Resolved regressions from bad pre-flight tests * Improved coverage support slightly * Related changes Changes in file tests/requirements.txt: * Version bumped related development extras
* This change is part of the review of PR #528 Changes in file tests/check_coverage_helper: * fix for quoting regression in helper
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/actions/check-control/action.yml (1)
64-88:⚠️ Potential issue | 🔴 CriticalInvalid
typeandoptionskeys in composite action inputs.The
type: choiceandoptionskeys (lines 70-74 forstatus, lines 81-88 forconclusion) are only valid forworkflow_dispatchinputs in workflow files, not for composite action inputs. Composite actions do not support typed/choice inputs - they only accept string values.This causes the actionlint parsing error: "unexpected key 'options' for definition of input 'conclusion'".
🔧 Proposed fix: Remove unsupported keys
status: description: | The check's status. See 'https://docs.github.com/en/rest/checks/runs?apiVersion=2022-11-28#update-a-check-run' for documentation. default: 'completed' required: false - type: choice - options: - - queued - - in_progress - - completed conclusion: description: | The check's conclusion. See 'https://docs.github.com/en/rest/checks/runs?apiVersion=2022-11-28#update-a-check-run' for documentation. default: '' required: false - type: choice - options: - - cancelled - - failure - - neutral - - success - - skipped - - timed_outConsider documenting the valid values in the description instead.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/actions/check-control/action.yml around lines 64 - 88, The inputs 'status' and 'conclusion' in the composite action currently use unsupported keys ("type: choice" and "options"); remove the unsupported keys from both input definitions (delete the type: choice and options: [...] blocks for the status and conclusion inputs) and keep them as simple string inputs (retain or adjust the default values if needed); instead, enumerate the allowed/expected values in each input's description for documentation and to avoid the actionlint "unexpected key 'options'" parsing error.
♻️ Duplicate comments (1)
tests/test_hear_server_activate.py (1)
147-150:⚠️ Potential issue | 🟡 MinorEnsure cleanup always runs and avoid masking test failures.
server.server_close()currently depends on reaching the end of the method (or can dereferenceNoneinfinally), so assertion/construction failures can leak sockets or hide the real error. Register cleanup immediately after construction and let exceptions fail naturally.Proposed fix
def test_initialization_with_valid_address(self): """ Test multicast server initialization with a valid address. @@ server = multicast.hear.McastServer(('224.0.0.1', self._the_test_port), None) + self.addCleanup(server.server_close) self.assertIsInstance(server, multicast.hear.McastServer) self.assertIsInstance(server, socketserver.UDPServer) - server.server_close() # Clean up def test_initialization_with_logger_name(self): @@ test_addr = ('239.0.0.9', self._the_test_port) server = multicast.hear.McastServer(test_addr, None) + self.addCleanup(server.server_close) self.assertIsNotNone(server.logger) self.assertTrue(server.logger.name.endswith('239.0.0.9')) - server.server_close() # Clean up def test_initialization_without_address(self): @@ host_test_fixtures = [None, (), (None, self._the_test_port)] _fail_fixture: str = "An expected logger was missing for the McastServer instance" for host_test_fixture in host_test_fixtures: with self.subTest(host_test_fixture=host_test_fixture): - server = None - _test_server_logger_name_cache = None - try: - server = multicast.hear.McastServer(host_test_fixture, None) - self.assertIsNotNone(server.logger, _fail_fixture) - _test_server_logger_name_cache = server.logger.name - except Exception as _cause: - context.debugtestError(_cause) - finally: - server.server_close() # Clean up + server = multicast.hear.McastServer(host_test_fixture, None) + self.addCleanup(server.server_close) + self.assertIsNotNone(server.logger, _fail_fixture) + _test_server_logger_name_cache = server.logger.name # assert to actually test self.assertEqual( _test_server_logger_name_cache, f"multicast.hear.McastServer.{multicast._MCAST_DEFAULT_GROUP}", # skipcq: PYL-W0212 ) # skipcq: PYL-W0212 - Test OKAlso applies to: 161-165, 181-190
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/test_hear_server_activate.py` around lines 147 - 150, Create the McastServer, then immediately register its cleanup with self.addCleanup(server.server_close) before running assertions so socket cleanup always runs even if assertions fail; update the three occurrences that construct multicast.hear.McastServer (the blocks using server = multicast.hear.McastServer(...), assertions that check isinstance(server, multicast.hear.McastServer) and isinstance(server, socketserver.UDPServer), and the current server.server_close() calls) to remove direct server.server_close() calls and instead rely on addCleanup(server.server_close) right after construction.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.coveragerc:
- Line 10: Update the .coveragerc to use the additive option exclude_also (not
exclude_lines) only if the project will run with coverage.py >= 7.2.0: change
any mention or use of exclude_lines where you intended to add patterns to
instead use exclude_also, and ensure the project dependency (or CI/test env)
pins or documents coverage.py 7.2.0+ so the additive behavior is supported;
verify the new exclude_also entries produce combined (default + custom)
exclusions rather than replacing defaults.
In @.github/actions/check-control/action.yml:
- Around line 326-329: The check creation curl flags use single-quoted strings
for 'output[summary]=${RAW_CHECK_SUMMARY_INPUT}' and
'output[text]=${RAW_CHECK_TEXT_INPUT}', preventing shell expansion; update those
flags in the action.yml step to use double quotes (e.g., -f
"output[summary]=${RAW_CHECK_SUMMARY_INPUT}" and -f
"output[text]=${RAW_CHECK_TEXT_INPUT}") so the RAW_CHECK_SUMMARY_INPUT and
RAW_CHECK_TEXT_INPUT variables are expanded before being sent to the GitHub API.
- Around line 358-361: In the complete_check step the output form fields are
wrapped in single quotes which prevents shell variable expansion; locate the -f
arguments that set 'output[summary]=${RAW_CHECK_SUMMARY_INPUT}' and
'output[text]=${RAW_CHECK_TEXT_INPUT}' (in the complete_check step) and replace
the single quotes with double quotes so the shell expands
RAW_CHECK_SUMMARY_INPUT and RAW_CHECK_TEXT_INPUT (i.e., change
'output[summary]=${RAW_CHECK_SUMMARY_INPUT}' and
'output[text]=${RAW_CHECK_TEXT_INPUT}' to use double quotes).
In @.github/workflows/Tests.yml:
- Line 158: Review and confirm the intended parallelism for the workflow jobs
(COVERAGE, DOCTESTS, INTEGRATION, EXTRAS-FOR-PIP) and update their max-parallel
values to match available runner capacity and desired concurrency; specifically
check the three occurrences where max-parallel is set (for COVERAGE and DOCTESTS
currently 3, INTEGRATION 4, EXTRAS-FOR-PIP 1) and either adjust the numeric
values to respect resource limits or document/justify them in the workflow
comment so they are intentional.
In `@Makefile`:
- Around line 180-184: The Makefile uses a shell variable DO_FAIL set on one
recipe line and invoked on subsequent lines (e.g., target MANIFEST.in and test
targets like just-test, test-mat-doctests, test-mat-*, test-extra, test-extra-*,
test-fuzzing, test-perf), but because each recipe line runs in its own shell
that assignment doesn't persist, masking failures; fix by replacing the
multi-line DO_FAIL pattern with an immediate failure check on the same recipe
line (use "|| exit N" or "|| { echo ...; exit N; }" as appropriate) so that
tests like the MANIFEST.in rule and every affected test-* target exit with the
correct status without relying on cross-line shell variable scope.
---
Outside diff comments:
In @.github/actions/check-control/action.yml:
- Around line 64-88: The inputs 'status' and 'conclusion' in the composite
action currently use unsupported keys ("type: choice" and "options"); remove the
unsupported keys from both input definitions (delete the type: choice and
options: [...] blocks for the status and conclusion inputs) and keep them as
simple string inputs (retain or adjust the default values if needed); instead,
enumerate the allowed/expected values in each input's description for
documentation and to avoid the actionlint "unexpected key 'options'" parsing
error.
---
Duplicate comments:
In `@tests/test_hear_server_activate.py`:
- Around line 147-150: Create the McastServer, then immediately register its
cleanup with self.addCleanup(server.server_close) before running assertions so
socket cleanup always runs even if assertions fail; update the three occurrences
that construct multicast.hear.McastServer (the blocks using server =
multicast.hear.McastServer(...), assertions that check isinstance(server,
multicast.hear.McastServer) and isinstance(server, socketserver.UDPServer), and
the current server.server_close() calls) to remove direct server.server_close()
calls and instead rely on addCleanup(server.server_close) right after
construction.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to data retention organization setting
📒 Files selected for processing (15)
.codecov.yml.coveragerc.github/actions/check-control/action.yml.github/workflows/CI-MATs.yml.github/workflows/Tests.ymlMakefileREADME.mddocs/requirements.txtmulticast/hear.pymulticast/recv.pypyproject.tomlrequirements.txttests/check_coverage_helpertests/requirements.txttests/test_hear_server_activate.py
* These changes are part of the review of PR #528 Changes in file .github/actions/check-control/action.yml: * Hardened input handling slightly
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/actions/check-control/action.yml (1)
197-203:⚠️ Potential issue | 🟠 MajorUse the provided workflow-run-id when building the default details URL.
Line 202 always uses
${{ github.run_id }}. In this branch, Line 201 already confirmedinputs.workflow-run-idis set, so the generated URL should use that input instead of the caller run ID.🔧 Proposed fix
- printf "details_url=%s\n" 'https://github.com/reactive-firewall-org/multicast/actions/runs/${{ github.run_id }}' >> "$GITHUB_OUTPUT" + printf "details_url=%s\n" 'https://github.com/reactive-firewall-org/multicast/actions/runs/${{ inputs.workflow-run-id }}' >> "$GITHUB_OUTPUT"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/actions/check-control/action.yml around lines 197 - 203, The default details URL branch incorrectly hardcodes github.run_id; update the printf that writes details_url so it uses the provided input variable (inputs.workflow-run-id) instead of github.run_id—i.e. replace the URL fragment '.../actions/runs/${{ github.run_id }}' with '.../actions/runs/${{ inputs.workflow-run-id }}' in the printf that sets details_url and keep the debug printf message that references inputs.workflow-run-id.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/actions/check-control/action.yml:
- Around line 324-327: The group label opened with "::group::validate-summary"
is misleading for the block that validates
RAW_CHECK_TEXT_INPUT/sanitized_input_text_field; rename the opening label to
match the content (for example "::group::validate-text" or
"::group::validate-input") so the group accurately reflects the validation of
RAW_CHECK_TEXT_INPUT and sanitized_input_text_field, leaving the "::endgroup::"
unchanged.
- Around line 149-173: The tag resolution sometimes returns annotated tag object
SHAs instead of commit SHAs; update the git rev-parse calls that resolve tags
(the branch/tag resolution logic that sets resolved_sha) to dereference tags to
their commit objects by using the ^{commit} suffix when calling git rev-parse
for refs/tags (so refs/tags/$input resolves to refs/tags/$input^{commit}), and
keep the existing validated check that resolved_sha is a 40-character commit SHA
before using it with the Checks API.
---
Outside diff comments:
In @.github/actions/check-control/action.yml:
- Around line 197-203: The default details URL branch incorrectly hardcodes
github.run_id; update the printf that writes details_url so it uses the provided
input variable (inputs.workflow-run-id) instead of github.run_id—i.e. replace
the URL fragment '.../actions/runs/${{ github.run_id }}' with
'.../actions/runs/${{ inputs.workflow-run-id }}' in the printf that sets
details_url and keep the debug printf message that references
inputs.workflow-run-id.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
.github/actions/check-control/action.yml
* These changes are part of the review of PR #528 Changes in file .github/actions/check-control/action.yml: * fixed a duplicate label Changes in file .github/workflows/Tests.yml: * improved stability slightly * improved GHA reporting slightly
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/actions/check-control/action.yml (1)
197-203:⚠️ Potential issue | 🟡 Minor
workflow-run-idis checked but not actually used in the generated URL.Line 201 gates on
inputs.workflow-run-id, but Line 202 still builds the URL withgithub.run_id. That makes customworkflow-run-idinputs ineffective and can emit the wrong details link.🔧 Proposed fix
- printf "details_url=%s\n" 'https://github.com/reactive-firewall-org/multicast/actions/runs/${{ github.run_id }}' >> "$GITHUB_OUTPUT" + printf "details_url=%s\n" 'https://github.com/reactive-firewall-org/multicast/actions/runs/${{ inputs.workflow-run-id }}' >> "$GITHUB_OUTPUT"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/actions/check-control/action.yml around lines 197 - 203, The URL generation wrongly ignores the provided inputs.workflow-run-id: when inputs.details-url is DEFAULT and inputs.workflow-run-id is non-empty the script still inserts github.run_id into the details_url; change the branch that handles the workflow-run-id check so it uses the inputs.workflow-run-id value to construct the printed URL (i.e., replace the hard-coded ${GITHUB_RUN_ID} usage with '${{ inputs.workflow-run-id }}' in the printf that writes details_url to $GITHUB_OUTPUT) and keep the debug message consistent (referencing inputs.workflow-run-id); ensure inputs.details-url, inputs.workflow-run-id and github.run_id are used in the correct branches.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/Tests.yml:
- Line 823: Fix the typo in the GitHub Actions step name by updating the step
label string "Summarize Syle-Tests" to the correct "Summarize Style-Tests"
wherever the workflow step name is defined (the string used as the step's name
in the YAML); ensure the change is applied to the step that summarizes style
tests so logs and UI show the corrected "Style" spelling.
---
Outside diff comments:
In @.github/actions/check-control/action.yml:
- Around line 197-203: The URL generation wrongly ignores the provided
inputs.workflow-run-id: when inputs.details-url is DEFAULT and
inputs.workflow-run-id is non-empty the script still inserts github.run_id into
the details_url; change the branch that handles the workflow-run-id check so it
uses the inputs.workflow-run-id value to construct the printed URL (i.e.,
replace the hard-coded ${GITHUB_RUN_ID} usage with '${{ inputs.workflow-run-id
}}' in the printf that writes details_url to $GITHUB_OUTPUT) and keep the debug
message consistent (referencing inputs.workflow-run-id); ensure
inputs.details-url, inputs.workflow-run-id and github.run_id are used in the
correct branches.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to data retention organization setting
📒 Files selected for processing (2)
.github/actions/check-control/action.yml.github/workflows/Tests.yml
* These changes are part of the review of PR #528 Changes in file .github/workflows/Tests.yml: * Cleanup Style step name Changes in file tests/check_coverage_helper: * Added minor changes for style and readability.
|
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/Tests.yml:
- Around line 808-822: The "Evaluate Style-Tests" step (id: styletests_outcome)
contains verbose bash logic to evaluate steps.style.outcome; replace the
multi-line if/then that sets THE_RESULT and exits with a single direct check on
steps.style.outcome and return the appropriate exit status (i.e., exit 0 for
success, non-zero otherwise) to simplify the block while preserving behavior;
update the run script for the styletests_outcome step to use the condensed
conditional referencing steps.style.outcome.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to data retention organization setting
📒 Files selected for processing (2)
.github/workflows/Tests.ymltests/check_coverage_helper
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
2 participants
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.
Release Candidate for Version 2.1.1 (v2.1.1rc2) Patch Notes
see full changelog: stable...master
Impacted GHI
run_selective.py#380Included and Superseded PR/MRs
Changelog
Changes in file .codecov.yml:
Changes in file .coderabbit.yaml:
Changes in file .coveragerc:
Changes in file docs/CI.md:
Changes in file docs/conf.py:
Changes in file docs/Environment_Configuration.md:
Changes in file docs/Exception_Guide.md:
Changes in file docs/FAQ.md:
Changes in file docs/index.md:
Changes in file docs/INSTALL.md:
Changes in file docs/Makefile:
Changes in file docs/requirements.txt:
=>0.46.2Changes in file docs/SECURITY.md:
Changes in file docs/Testing.md:
Changes in file docs/toc.md:
Changes in file docs/USAGE.md:
Changes in file docs/utils.py:
Changes in file generate_manifest.sh:
Additions with file generate_manifest.sh:
Changes in file .github/actions/check-control/action.yml:
Changes in file .github/actions/checkout-and-rebuild/action.yml:
Changes in file .github/actions/run-minimal-acceptance-tests/action.yml:
Changes in file .github/actions/setup-py-reqs/action.yml:
Changes in file .github/actions/test-reporter-upload/action.yml:
Changes in file .github/CONTRIBUTING.md:
Changes in file .github/ISSUE_TEMPLATE/bug_report.md:
Changes in file .github/ISSUE_TEMPLATE.md:
Changes in file .github/labeler.yml:
Changes in file .github/tools/checkmake.bash:
Changes in file .github/tools/cioutput.py:
Changes in file .github/tools/fetch-test-reporter:
Changes in file .github/workflows/bandit.yml:
Changes in file .github/workflows/CD-PyPi.yml:
ensure shell is running bash
Changes in file .github/workflows/CI-BUILD.yml:
Changes in file .github/workflows/CI-CHGLOG.yml:
Changes in file .github/workflows/CI-DOCS.yml:
Changes in file .github/workflows/CI-MATs.yml:
Changes in file .github/workflows/codeql-analysis.yml:
Changes in file .github/workflows/flake8.yml:
Changes in file .github/workflows/makefile-lint.yml:
Changes in file .github/workflows/markdown-lint.yml:
Changes in file .github/workflows/scorecard.yml:
Changes in file .github/workflows/shellcheck.yml:
Changes in file .github/workflows/Tests.yml:
Changes in file .github/workflows/yaml-lint.yml:
Changes in file .gitmodules:
Changes in file LICENSE.md:
Changes in file Logo.svg:
Changes in file Makefile:
Changes in file docs/Makefile:
=>0.46.2Changes in file multicast/env.py:
Changes in file multicast/exceptions.py:
Changes in file multicast/hear.py:
Changes in file multicast/init.py:
Changes in file multicast/main.py:
Changes in file multicast/recv.py:
Changes in file multicast/send.py:
Changes in file multicast/skt.py:
Changes in file pyproject.toml:
=>0.46.2Changes in file README.md:
Changes in file tests/requirements.txt:
Changes in file requirements.txt:
Changes in file docs/requirements.txt:
=>0.46.2Changes in file tests/check_cc_lines:
Changes in file tests/check_CEP5_regression.bash:
Changes in file tests/check_CEP5_regression:
Additions with file tests/check_CEP5_regression.bash:
Changes in file tests/check_CEP5_regression.bash:
Additions with file tests/check_CEP5_regression.bash:
Changes in file tests/check_codecov:
Changes in file tests/check_coverage_helper:
Additions with file tests/check_coverage_helper:
Changes in file tests/check_integration_coverage:
Changes in file tests/check_pip:
Changes in file tests/check_spelling:
Changes in file tests/context.py:
Changes in file tests/init.py:
Changes in file tests/MulticastUDPClient.py:
Changes in file tests/profiling.py:
Changes in file tests/requirements.txt:
=>0.46.2Changes in file tests/run_selective.py:
Changes in file tests/test_basic.py:
Changes in file tests/test_build.py:
Changes in file tests/test_deps.py:
Changes in file tests/test_exceptions.py:
Changes in file tests/test_extra.py:
Changes in file tests/test_fuzz.py:
Changes in file tests/test_hear_cleanup.py:
Changes in file tests/test_hear_data_processing.py:
Changes in file tests/test_hear_keyboard_interrupt.py:
Changes in file tests/test_hear_server_activate.py:
passstatement to resolve false PYL-W0107 flagging of a test fixture.Changes in file tests/test_hear_server.py:
Changes in file tests/test_manifest.py:
Changes in file tests/test_recv.py:
Changes in file tests/test_usage.py:
Changes in file tox.ini:
Full Changelog:
stable...masterSummary by CodeRabbit