You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using the CLI, you can run into filesystem errors which don't clearly describe what the issue is.
These error messages should be more descriptive, pointing users to solutions. As a quality of life feature for output directories, any nonexistent directories should be created during execution.
...will cause the following generic and unclear filesystem error on Windows if no ./network directory exists:
Error: The system cannot find the path specified. (os error 3)
A similar error,
Error: The system cannot find the file specified. (os error 2)
...is output if the path provided to the config file is invalid.
Alternatives
Both of these are minor issues, so creating the directories in question and/or ensuring file paths are correct both work. The docs could also cover these common mistakes.
The text was updated successfully, but these errors were encountered:
Describe your feature
While using the CLI, you can run into filesystem errors which don't clearly describe what the issue is.
These error messages should be more descriptive, pointing users to solutions. As a quality of life feature for output directories, any nonexistent directories should be created during execution.
Examples
For instance, a config that looks like this
...will cause the following generic and unclear filesystem error on Windows if no
./network
directory exists:A similar error,
...is output if the path provided to the config file is invalid.
Alternatives
Both of these are minor issues, so creating the directories in question and/or ensuring file paths are correct both work. The docs could also cover these common mistakes.
The text was updated successfully, but these errors were encountered: