-
-
Notifications
You must be signed in to change notification settings - Fork 745
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
release 0.9.0 #2239
base: master
Are you sure you want to change the base?
release 0.9.0 #2239
Conversation
Dev/v0.7.0
update the version and dependent libs.
[CoreEngine] remove the deprecated files in the scheduler.
…gging Inference Gateway Logs
…/FedML into raphael/fix-multi-subfd
[Deploy] Recursively find the model serving package folder
[Deploy] Hot fix grammar.
…tfix Hot fix to support local debugging
…n Windows OS. 2. fixed the issue the sqlite path is illegal in Windows OS.
[CoreEngine] 1. fixed the issue that the fork method is not support i…
…counter Adding hash set for counting the number of pending requests per endpoint.
…d_urls Moving from storage object to presigned URLs
[Deploy] Refactor the quick start example, use public ip as default.
…ed architecture that supports Launch Master, Launch Slave, Deploy Master, and Deploy Slave at the same time.
…ateway performance
…disable MQTT debug logging
update dev/0.7.0 to charlie dev branch
Deployment and Inference Module Performance Optimization Project
logging.info("=" * 80) | ||
logging.info("[Device Model Deployment] Creating container with following parameters:") | ||
logging.info("=" * 80) | ||
logging.info("Image: {}".format(inference_image_name)) |
Check failure
Code scanning / CodeQL
Clear-text logging of sensitive information High
sensitive data (password)
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix AI 26 days ago
To fix the problem, we should avoid logging any potentially sensitive information. Instead of logging the inference_image_name
directly, we can log a sanitized version or avoid logging it altogether. We should also review other logging statements to ensure no sensitive information is being logged.
The best way to fix this without changing existing functionality is to sanitize the inference_image_name
before logging it. We can replace sensitive parts of the string with a placeholder or simply avoid logging it if it contains sensitive information.
-
Copy modified lines R224-R225
@@ -223,3 +223,4 @@ | ||
logging.info("=" * 80) | ||
logging.info("Image: {}".format(inference_image_name)) | ||
sanitized_inference_image_name = inference_image_name.replace(registry_user_password, "****") if registry_user_password in inference_image_name else inference_image_name | ||
logging.info("Image: {}".format(sanitized_inference_image_name)) | ||
logging.info("Container name: {}".format(default_server_container_name)) |
[debug] Remove verbose logging in job monitor
No description provided.