Change level of log message to DEBUG - #223
Merged
Merged
Conversation
|
Great job! No new security vulnerabilities introduced in this pull request |
cx-happy-yang
approved these changes
Aug 20, 2026
cx-happy-yang
added a commit
that referenced
this pull request
Sep 2, 2026
* Bump version to 1.9.1 and update changelog Covers the merged changes since 1.9.0: - Update ScanParameter DTO (#222) - Change level of log message to DEBUG (#223) * Add AI Triage 404 fix to 1.9.1 changelog entry Anticipates the fix/ai-triage-url-encode-group-id PR merging before this version bump PR.
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.
An alternative to changing the level to DEBUG would be to remove the log statement altogether. It seems that only a small number of the SDK functions/methods have such log statements.