Skip to content

I 126: clear logging - #133

Closed
al-niessner wants to merge 3 commits into
mainfrom
i-126
Closed

al-niessner wants to merge 3 commits into
mainfrom
i-126

Conversation

@al-niessner

@al-niessner al-niessner commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

🗒️ Summary

Logging is clear but more resolved than you may want to make sure it is clear. See HarvestCmd.printSummay() changes for details.

🤖 AI Assistance Disclosure

  • No AI assistance used
  • AI used for light assistance (e.g., suggestions, refactoring, documentation help, minor edits)
  • AI used for moderate content generation (AI generated some code or logic, but the developer authored or heavily revised the majority)
  • AI generated substantial portions of this code

Estimated % of code influenced by AI: 0 %

⚙️ Test Data and/or Report

♻️ Related Issues

Closes #126

🤓 Reviewer Checklist

Reviewers: Please verify the following before approving this pull request.

Documentation and PR Content

  • Documentation: README, Wiki, or inline documentation (Sphinx, Javadoc, Docstrings) have been updated to reflect these changes.
  • Issue Traceability: The PR is linked to a valid GitHub Issue
  • PR Title: The PR title is "user-friendly" clearly identifying what is being fixed or the new feature being added, that if you saw it in the Release Notes for a tool, you would be able to get the gist of what was done.

Security & Quality

  • SonarCloud: Confirmed no new High or Critical security findings.
  • Secrets Detection: Verified that the Secrets Detection scan passed and no sensitive information (keys, tokens, PII) is exposed.
  • Code Quality: Code follows organization style guidelines and best practices for the specific language (e.g., PEP 8, Google Java Style).

Testing & Validation

  • Test Accuracy: Verified that test data is accurate, representative of real-world PDS4 scenarios, and sufficient for the logic being tested.
  • Coverage: Automated tests cover new logic and edge cases.
  • Local Verification: (If applicable) Successfully built and ran the changes in a local or staging environment.

Maintenance

  • Backward Compatibility: Confirmed that these changes do not break existing downstream dependencies or API contracts (or that breaking changes are clearly documented).

@al-niessner
al-niessner requested a review from a team as a code owner July 24, 2026 17:21
@sonarqubecloud

Copy link
Copy Markdown

@al-niessner

Copy link
Copy Markdown
Contributor Author

superseded by #137

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

Labels

None yet

Projects

None yet

1 participant