Skip to content

fix(parsers): wrap over-long log line in sompasensecap (E501)#40

Open
laurigates wants to merge 1 commit into
masterfrom
fix/sompasensecap-e501
Open

fix(parsers): wrap over-long log line in sompasensecap (E501)#40
laurigates wants to merge 1 commit into
masterfrom
fix/sompasensecap-e501

Conversation

@laurigates

Copy link
Copy Markdown
Member

What

Split a 147-char warning f-string in fvhiot/parsers/sompasensecap.py into two implicitly-concatenated strings so it fits the 120-char ruff limit. Message text is unchanged.

Why

The tests CI job is ruff check --output-format=github .. The f-string introduced in #38 triggered E501 Line too long (147 > 120), failing CI on master across all three Python versions (3.10/3.11/3.12) — and consequently on every open PR (including the Renovate onboarding PR #39).

Verification

uvx ruff check .All checks passed! locally; pre-commit ruff hook passed on push.

🤖 Generated with Claude Code

The warning f-string introduced in #38 was 147 chars, exceeding the
120-char ruff limit and failing the tests (ruff check) CI job on master.
Split into two implicitly-concatenated strings; message text unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@laurigates laurigates self-assigned this Jun 4, 2026
@laurigates laurigates added the chore Maintenance, dependency updates, refactoring label Jun 4, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request splits a long logging warning string into two lines in fvhiot/parsers/sompasensecap.py to improve readability. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Maintenance, dependency updates, refactoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant