fix(#1984): gate the GG SPLICE FUNCS trace behind --debug - #2384
Merged
Conversation
galaxyscope.py's worker had a bare print("GG SPLICE FUNCS:", ...) next to
the "# --- INJECTED DEBUG TRACE ---" marker, firing unconditionally on
every file of every real scan (and into CI logs). Convert it to a
logger.debug [WORKER-TRACE] line matching its neighbours, guarded by
isEnabledFor(DEBUG) so the list comp is skipped when not tracing.
Closes #1984.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #1984.
galaxyscope.py's_process_file_workerhad a bareprint("GG SPLICE FUNCS:", [f["name"] for f in ...])sitting next to the# --- INJECTED DEBUG TRACE ---marker. It fired unconditionally on everyfile of every real scan — straight to stdout, including CI logs (visible
flooding
crucible_check.pyoutput during this session).Converted to a
logger.debug[WORKER-TRACE]line matching the twologger.debug(f"[WORKER-TRACE] ...")calls that already bracket it,guarded by
logger.isEnabledFor(logging.DEBUG)(the same patternlanguage_lens.pyuses) so the list comprehension is skipped entirelywhen not tracing.
Cosmetic/noise only — no output-correctness change.
test_galaxyscope.py46/46 pass; ruff / mypy / dead-key / ast-accuracy clean.
🤖 Generated with Claude Code