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
I am using an Apple M3 Max, Sonoma Version 14.1.2 (23B2091), using path-io v1.8.1.
I just spent some time debugging a personal project of mine, trying to figure out why ensureDir (more generally createDir).
In my application, I am currently just simply storing a json config in the application directory. However, when using stack, this executable is in a directory where all privileges except searchable are given.
When using ensureDir to make sure a subdirectory exists to write some files into, the application throws an error:
myApp-exe: /path/to/.../.stack-work/install/aarch64-osx/.../bin/myApp-exe: createDirectory: inappropriate type (Not a directory)
The docs specify:
InappropriateType The path refers to an existing non-directory object. [EEXIST]
But this didn't really help in solving the problem.
While this is clearly an issue for me to better manage in my application to avoid this problem, either better documentation or reporting would be helpful.
Thanks
The text was updated successfully, but these errors were encountered:
I am using an Apple M3 Max, Sonoma Version 14.1.2 (23B2091), using
path-io
v1.8.1.I just spent some time debugging a personal project of mine, trying to figure out why
ensureDir
(more generallycreateDir
).In my application, I am currently just simply storing a json config in the application directory. However, when using stack, this executable is in a directory where all privileges except searchable are given.
When using
ensureDir
to make sure a subdirectory exists to write some files into, the application throws an error:The docs specify:
But this didn't really help in solving the problem.
While this is clearly an issue for me to better manage in my application to avoid this problem, either better documentation or reporting would be helpful.
Thanks
The text was updated successfully, but these errors were encountered: