fix(tasks): remove debug print statements causing log spam#348
Merged
MoralCode merged 1 commit intoMay 27, 2026
Merged
Conversation
These print(libdays) statements were outputting bare numbers to stdout during dependency libyear analysis, creating log spam in task logs. Removed from both util.py and pypi_libyear_util.py — addressed the root cause of issue #289. Signed-off-by: Suraj <surajh6705@gmail.com>
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
2 participants
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.
What problem does this solve?
Removes two debug
print(libdays)statements that were outputting bare numbers to stdout during dependency libyear analysis, causing log spam reported in issue #289.What changed and why?
Removed
print(libdays)from two locations:collectoss/tasks/git/dependency_libyear_tasks/libyear_util/util.pycollectoss/tasks/git/dependency_libyear_tasks/libyear_util/pypi_libyear_util.pyThese debug prints were left in the codebase and caused the log noise:
0,497,932, etc. appearing in task logs.How was this tested?
Checklist
This contribution was created with AI assistance, with human review and approval at each step.