chore(micro-fix): fix debug logging level in graph executor #4380
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type: Micro-fix
This PR adjusts a debug logging statement to use the appropriate logging level.
Changes
logger.info()tologger.debug()incore/framework/graph/executor.py:371Why This Qualifies as a Micro-fix
✅ < 20 lines changed (only 1 line)
✅ No logic, API, or database changes
✅ Linting/cleanup category (logging best practices)
✅ Zero risk of breaking changes
Per CONTRIBUTING.md, micro-fixes can be submitted without prior issue assignment.
Problem
Debug-level information was appearing in production logs at INFO level, adding noise to log output.
Solution
Use the appropriate
debuglogging level so the message only appears when debug logging is explicitly enabled.Testing
ruff checkpasses (linting) - all files cleanruff format --checkpasses (formatting) - 239 files already formattedpytest tests/passes - 683 tests passed, 0 failedChecklist
micro-fixfor fast-track review[micro-fix,code-quality,logging,chore]