Skip to content
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

The value of log.to cannot be configured as a non-existent path #4147

Closed
1 of 11 tasks
FoundAdd opened this issue Apr 10, 2024 · 2 comments
Closed
1 of 11 tasks

The value of log.to cannot be configured as a non-existent path #4147

FoundAdd opened this issue Apr 10, 2024 · 2 comments

Comments

@FoundAdd
Copy link

Describe the feature request

If I configure log.to with a path that does not exist, the logging system will not automatically create this directory, but will directly prompt "no such file or directory".
image

Describe alternatives you've considered

It would be much more convenient if the logic could be changed to automatically create lower-level directories. Currently, the corresponding log directory can only be created in advance.

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
@fatedier
Copy link
Owner

Please use the latest version and use explicit paths instead of environment variables.

Copy link

github-actions bot commented May 3, 2024

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants