fix: Add null-handling for static cache path in async logger #5889
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.
This PR is derived from #5572 in an effort to make the large amount of changes easier to review for #5577.
The async logger relies on a nullable static caches path, so we need to unwrap it before we check for existence. As we are already logging an error and exiting the method, when directory creation fails, I use the same approach when the cache directory is not defined.
#skip-changelog