[hermes] atlasbot: python:S2208 #139
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
SonarQube reports python:S2208 in
atlasbot/engine/answerer/spine.py. The build is green; this is a standing finding, not a failure.What is wrong
Line 9 uses a wildcard import (
from ._base import *), which hides which names actually enter the module namespace. Notably, no name from_baseis referenced anywhere in this file's code — the star import only matters because the dynamically computed__all__at the bottom of the file re-exports every underscore-prefixed name inglobals(), so any underscore names that_base.__all__exposes are silently re-exported throughspine.Ariadne opened no pull request for it: no automated patch was possible for this finding.
Facts
atlasbot/engine/answerer/spine.py:9)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.
atlasbot/engine/answerer/spine.py— Replace the wildcard with an explicit import of exactly the names that_base.__all__currently exports (those are the only names a star import binds when__all__is defined; without an__all__, a star import skips underscore-prefixed names entirely, in which case the import is dead and should simply be deleted). Because the module's own__all__is built fromglobals(), explicitly imported underscore names are still picked up and re-exported exactly as before, so behaviour is unchanged. The maintainer should substitute the real names fromatlasbot/engine/answerer/_base.py's `all... (truncated)
Links
/api/admin/audit/events, event typeshermes_autotriage_incidentandhermes_autotriage_diagnosis.Filed automatically by Ariadne from a Hermes Agent diagnosis (run run_1201d6d55fe142319007e8520b864423). Hermes has no write access to this repository; no files or infrastructure were changed.