[hermes] atlasbot: python:S1871 #140

Open
opened 2026-09-26 16:22:00 +00:00 by hermes-automation · 0 comments

SonarQube reports python:S1871 in atlasbot/matrix/bot.py. The build is green; this is a standing finding, not a failure.

What is wrong

In the heartbeat() closure, the if/elif at lines 167-170 both set should_send = True in their bodies, so the branch on line 168 and the branch on line 170 are byte-for-byte identical, which is exactly what S1871 flags — the branching adds no behavioral difference, only the condition matters.

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

Facts

  • gitea — Either merge this branch with the identical one on line "168" or change one of the implementations. (MAJOR, 10min estimated) (atlasbot/matrix/bot.py:170)

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/matrix/bot.py — Collapse the if/elif into a single boolean assignment using 'or' so there is only one place assigning should_send = True. Python's short-circuit evaluation of 'or' preserves the exact original control flow (the second condition is still only evaluated when the first is falsy), so behavior is unchanged.

should_send = (snippet and snippet != last_note) or (
                    now - last_sent >= max(60.0, self._settings.thinking_interval_sec * 2)
                )
                if should_send:

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

SonarQube reports **python:S1871** in `atlasbot/matrix/bot.py`. The build is green; this is a standing finding, not a failure. ## What is wrong In the heartbeat() closure, the if/elif at lines 167-170 both set should_send = True in their bodies, so the branch on line 168 and the branch on line 170 are byte-for-byte identical, which is exactly what S1871 flags — the branching adds no behavioral difference, only the condition matters. Ariadne opened no pull request for it: no automated patch was possible for this finding. ## Facts - **gitea** — Either merge this branch with the identical one on line "168" or change one of the implementations. (MAJOR, 10min estimated) (`atlasbot/matrix/bot.py:170`) ## 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/matrix/bot.py`** — Collapse the if/elif into a single boolean assignment using 'or' so there is only one place assigning should_send = True. Python's short-circuit evaluation of 'or' preserves the exact original control flow (the second condition is still only evaluated when the first is falsy), so behavior is unchanged. ``` should_send = (snippet and snippet != last_note) or ( now - last_sent >= max(60.0, self._settings.thinking_interval_sec * 2) ) if should_send: ``` ## Links - SonarQube finding: https://quality.bstein.dev/project/issues?resolved=false&id=atlasbot&open=AZ2y3T24Ky9i4pkIpSiI - 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_f16db5ffe9f74c3db64a435e9b36cd2f](https://triage.bstein.dev/chat?resume=run_f16db5ffe9f74c3db64a435e9b36cd2f)). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=atlasbot classification=python:S1871 incident=sonar/atlasbot/python:S1871/AZ2y3T24Ky9i4pkIpSiI -->
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bstein/atlasbot#140
No description provided.