-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Files missing read permission #1818
Comments
We haven't changed the behavior between versions, but it's likely a configuration in your filesystem settings (check your For example, on my machine, all new files created by the ODM container are:
While ODM could check/add permissions while creating new files, I don't think ODM should be in charge of doing so. 🙏 |
Agree that it wouldn't make much sense for ODM to check and change permissions ;) But still think this is a problem that applies to some versions of ODM. Also note that it is only the files -rw------- 1 root root opensfm/undistorted/openmvs/scene_dense.ply all other files have My initial guess would be that something have changed in https://github.com/cdcseacave/openMVS between builds, if that can make sense? |
Ah, I didn't realize this only affected certain files 🙏 Your guess might be correct: https://github.com/cdcseacave/openMVS/blob/develop/libs/Common/File.h#L499 |
Thanks, I did a test and rebuilt ODM v3.3.0 with h = ::open(aFileName, m, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); in openMVS File.h#L471, and that looks to solve the problem. This isn't a big problem, but it's subtle enough to create some headache. |
Thanks for testing; I've brought this change into our fork and will be solved with #1833 |
How did you install ODM? (Docker, installer, natively, ...)?
Docker
What is the problem?
The files:
-rw------- 1 root root opensfm/undistorted/openmvs/scene_dense.ply
-rw------- 1 root root opensfm/undistorted/openmvs/scene_dense_dense_filtered.ply
-rw------- 1 root root odm_meshing/odm_mesh.ply
-rw------- 1 root root odm_meshing/odm_25dmesh.ply
Are created with permission 600 so they aren't readable by others without changing permissions using the root user.
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
The above files should be created with permission 644 so they are readable by everyone, this is the behavior in ODM v3.1.0.
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
The text was updated successfully, but these errors were encountered: