[hermes] ariadne: python:S2208 #143

New Issue

hermes-automation · 2026-10-29T17:19:12Z

hermes-automation commented

2026-10-29 17:19:12 +00:00

SonarQube reports python:S2208 in ariadne/services/cluster_state_profiles.py. The build is green; this is a standing finding, not a failure.

What is wrong

The module uses a wildcard import from cluster_state_contract, obscuring its actual dependencies and triggering Sonar rule S2208. Replace it with explicit imports for the two constants used locally and the two contract types deliberately re-exported in all.

Ariadne opened no pull request for it: no automated patch was possible for this finding.

Facts

gitea — Import only needed names or import the module and then use its members. (CRITICAL, 5min estimated) (ariadne/services/cluster_state_profiles.py:5)

Suggested fix (not applied)

Hermes could not open a pull request for this, so the change below was not written, validated, or pushed anywhere. It is a starting point for whoever picks this up, not a reviewed patch.

ariadne/services/cluster_state_profiles.py — The wildcard import imports every public name from cluster_state_contract even though this module only needs _NODE_WORKLOAD_TOP, _PROFILE_LIMIT, ClusterStateSummary, and SignalContext. Explicitly importing those names preserves the existing runtime behavior and public re-exports while making dependencies clear.

from .cluster_state_contract import (
    ClusterStateSummary,
    SignalContext,
    _NODE_WORKLOAD_TOP,
    _PROFILE_LIMIT,
)

Links

SonarQube finding: https://quality.bstein.dev/project/issues?resolved=false&id=ariadne&open=AZ2y0FYFKy9i4pkIpNlV
Full evidence bundle and audit trail live in Ariadne at /api/admin/audit/events, event types hermes_autotriage_incident and hermes_autotriage_diagnosis.

Filed automatically by Ariadne from a Hermes Agent diagnosis (run run_64ee712c7eb04da292f43fffc851fc38). Hermes has no write access to this repository; no files or infrastructure were changed.

SonarQube reports **python:S2208** in `ariadne/services/cluster_state_profiles.py`. The build is green; this is a standing finding, not a failure. ## What is wrong The module uses a wildcard import from cluster_state_contract, obscuring its actual dependencies and triggering Sonar rule S2208. Replace it with explicit imports for the two constants used locally and the two contract types deliberately re-exported in __all__. Ariadne opened no pull request for it: no automated patch was possible for this finding. ## Facts - **gitea** — Import only needed names or import the module and then use its members. (CRITICAL, 5min estimated) (`ariadne/services/cluster_state_profiles.py:5`) ## Suggested fix (not applied) Hermes could not open a pull request for this, so the change below was not written, validated, or pushed anywhere. It is a starting point for whoever picks this up, not a reviewed patch. **`ariadne/services/cluster_state_profiles.py`** — The wildcard import imports every public name from cluster_state_contract even though this module only needs _NODE_WORKLOAD_TOP, _PROFILE_LIMIT, ClusterStateSummary, and SignalContext. Explicitly importing those names preserves the existing runtime behavior and public re-exports while making dependencies clear. ``` from .cluster_state_contract import ( ClusterStateSummary, SignalContext, _NODE_WORKLOAD_TOP, _PROFILE_LIMIT, ) ``` ## Links - SonarQube finding: https://quality.bstein.dev/project/issues?resolved=false&id=ariadne&open=AZ2y0FYFKy9i4pkIpNlV - Full evidence bundle and audit trail live in Ariadne at `/api/admin/audit/events`, event types `hermes_autotriage_incident` and `hermes_autotriage_diagnosis`. Filed automatically by Ariadne from a Hermes Agent diagnosis (run [run_64ee712c7eb04da292f43fffc851fc38](https://triage.bstein.dev/chat?resume=run_64ee712c7eb04da292f43fffc851fc38)). Hermes has no write access to this repository; no files or infrastructure were changed.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: titan/ariadne#143