[hermes] ananke: go:S1192 #153

New Issue

hermes-automation · 2026-09-22T05:20:01Z

hermes-automation commented

2026-09-22 05:20:01 +00:00

SonarQube reports go:S1192 in internal/cluster/orchestrator_longhorn_reconcile.go. The build is green; this is a standing finding, not a failure.

What is wrong

The namespace literal "longhorn-system" is duplicated in three query argument lists, triggering go:S1192 and creating multiple places to maintain the same value. Extracting it into one constant preserves the exact commands and runtime behavior.

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

Facts

gitea — Define a constant instead of duplicating this literal "longhorn-system" 3 times. (CRITICAL, 6min estimated) (internal/cluster/orchestrator_longhorn_reconcile.go:136)

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.

internal/cluster/orchestrator_longhorn_reconcile.go — Add the package-level constant after the imports, then replace the namespace literal in queryLonghornNodes, queryLonghornManagerDaemonSet, and longhornManagerPodsByNode with that constant. The snippets below show the declaration and the three replacement statements; leave all surrounding code unchanged.

const longhornNamespace = "longhorn-system"

// In queryLonghornNodes:
out, err := o.kubectl(ctx, 30*time.Second, "-n", longhornNamespace, "get", "nodes.longhorn.io", "-o", "json")

// In queryLonghornManagerDaemonSet:
out, err := o.kubectl(ctx, 20*time.Second, "-n", longhornNamespace, "get", "daemonset", "longhorn-manager", "-o", "json")

// In longhornManagerPodsByNode:
args := []string{"-n", longhornNamespace, "get", "pods", "-o", "json"}

Links

SonarQube finding: https://quality.bstein.dev/project/issues?resolved=false&id=ananke&open=AZ-IckL-1fRfbdzqD-5R
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_7947fddbab674580bd17c6fab57af38e). Hermes has no write access to this repository; no files or infrastructure were changed.

SonarQube reports **go:S1192** in `internal/cluster/orchestrator_longhorn_reconcile.go`. The build is green; this is a standing finding, not a failure. ## What is wrong The namespace literal "longhorn-system" is duplicated in three query argument lists, triggering go:S1192 and creating multiple places to maintain the same value. Extracting it into one constant preserves the exact commands and runtime behavior. Ariadne opened no pull request for it: no automated patch was possible for this finding. ## Facts - **gitea** — Define a constant instead of duplicating this literal "longhorn-system" 3 times. (CRITICAL, 6min estimated) (`internal/cluster/orchestrator_longhorn_reconcile.go:136`) ## 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. **`internal/cluster/orchestrator_longhorn_reconcile.go`** — Add the package-level constant after the imports, then replace the namespace literal in queryLonghornNodes, queryLonghornManagerDaemonSet, and longhornManagerPodsByNode with that constant. The snippets below show the declaration and the three replacement statements; leave all surrounding code unchanged. ``` const longhornNamespace = "longhorn-system" // In queryLonghornNodes: out, err := o.kubectl(ctx, 30*time.Second, "-n", longhornNamespace, "get", "nodes.longhorn.io", "-o", "json") // In queryLonghornManagerDaemonSet: out, err := o.kubectl(ctx, 20*time.Second, "-n", longhornNamespace, "get", "daemonset", "longhorn-manager", "-o", "json") // In longhornManagerPodsByNode: args := []string{"-n", longhornNamespace, "get", "pods", "-o", "json"} ``` ## Links - SonarQube finding: https://quality.bstein.dev/project/issues?resolved=false&id=ananke&open=AZ-IckL-1fRfbdzqD-5R - 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_7947fddbab674580bd17c6fab57af38e](https://triage.bstein.dev/chat?resume=run_7947fddbab674580bd17c6fab57af38e)). 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/ananke#153