Aller au contenu
login
arrow_backRetour aux issues
squid-protocol/gitgalaxy #1984

Leftover debug print("GG SPLICE FUNCS", ...) in galaxyscope.py fires on every real scan

ecoDébutant good first issue refactor priority: low

descriptionDescription

## Summary `gitgalaxy/galaxyscope.py:429` has a bare `print("GG SPLICE FUNCS:", [f["name"] for f in logic_data.get("functions", [])])` sitting right next to a comment labeled `# --- INJECTED DEBUG TRACE ---` (line ~405). This fires unconditionally on every file processed by the real pipeline (not gated behind `--debug`/a log level check) -- confirmed noisy on every `galaxyscope --db-only` invocation during this session's work on #1973/#1974/#1975/#1972, printing every extracted function name for every file scanned directly to stdout. ## Impact Cosmetic/noise only -- doesn't affect correctness of any output, just clutters stdout on every real scan (including in CI logs, presumably). Low priority, but a quick, safe removal. ## Suggested fix Delete the `print(...)` call, or if the trace is still useful for real debugging, convert it to `logger.debug(...)` (matching the neighboring `logger.debug(f"[WORKER-TRACE] ...")` calls' own convention, which already exist right next to it) so it's opt-in rather than always-on.
codeOuvre sur GitHub