-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Code QA Fixes) - Use LoggingCallbackManager
to ensure no dup callbacks are added
#8070
base: main
Are you sure you want to change the base?
Conversation
β¦rect dict comparison
The latest updates on your projects. Learn more about Vercel for Git βοΈ
|
parent_list.append(callback) | ||
else: | ||
verbose_logger.debug( | ||
f"Callback {callback} already exists in {parent_list}, not adding again.." |
Check failure
Code scanning / CodeQL
Clear-text logging of sensitive information High
sensitive data (secret)
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix AI 6 days ago
To fix the problem, we should avoid logging sensitive information directly. Instead, we can log a generic message that does not include the sensitive data. This way, we maintain the logging functionality without exposing sensitive information.
- Replace the logging statement that includes the sensitive
callback
data with a more generic message. - Specifically, change the logging statement in the
_add_string_callback_to_list
method inlitellm/litellm_core_utils/logging_callback_manager.py
.
-
Copy modified line R103
@@ -102,3 +102,3 @@ | ||
verbose_logger.debug( | ||
f"Callback {callback} already exists in {parent_list}, not adding again.." | ||
"A callback already exists in the list, not adding again." | ||
) |
(Code QA Fixes) - Use
LoggingCallbackManager
to ensure no dup callbacks are addedRelevant issues
Type
π New Feature
π Bug Fix
π§Ή Refactoring
π Documentation
π Infrastructure
β Test
Changes
[REQUIRED] Testing - Attach a screenshot of any new tests passing locally
If UI changes, send a screenshot/GIF of working UI fixes