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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this change correctly removes the API key from being logged, which is a critical security improvement, it's worth noting that using
print()for logging application status is not ideal. It would be better to use a proper logging framework, like Python'sloggingmodule. This would provide more flexibility, such as controlling log verbosity and directing logs to different outputs (e.g., stderr or a file), separating them from the primary output of the CLI tool. The project already seems to have a logger set up in other modules (e.g.,dashscope.utils.oss_utils), which could be leveraged here as well for better consistency.