Fix user_config_dir()
for GCP/AWS functions
#4726
Merged
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.
Compatibility fix for GCP functions and AWS lambda for user config directory in #4628
🛠️ PR Summary
Made with ❤️ by Ultralytics Actions
🌟 Summary
Enhanced user configuration directory handling, including write permissions check.
📊 Key Changes
user_config_dir
to improve readability./tmp
for Linux systems where only/tmp
is writable.is_writeable
to verify write access to a given path.🎯 Purpose & Impact
user_config_dir
function works correctly in environments with restricted write access, such as Google Cloud Functions or AWS Lambda.