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've encountered a nasty error that occurs when target directories do not have execute permissions for the user.
The code below will replicate the issue:
importos,vcs,shutil,statimportnumpyasnpnp.warnings.filterwarnings('ignore') ; # Turn off warnings# Change to tmp diros.chdir('/export/duro/tmp')
data=np.random.rand(10,10)
x=vcs.init(bg=True,geometry=(100,100))
x.plot(data)
ifos.path.exists('test'):
shutil.rmtree('test') ; # Remove existing directoryos.mkdir('test') ; # Default perms 700mode=stat.S_IMODE(os.stat('test').st_mode)
printmodex.png('test/test1.png')
print'png written'os.chmod('test',600) # Mode from rwx to rw-mode=stat.S_IMODE(os.stat('test').st_mode)
printmodex.png('test/test2.png')
The error is:
ERROR: In /export/dout/miniconda2/conda-bld/vtk-cdat_1503063744037/work/IO/Image/vtkPNGWriter.cxx, line 276
vtkPNGWriter (0x2f5dcc0): Unable to open file test/test2.png
ERROR: In /export/dout/miniconda2/conda-bld/vtk-cdat_1503063744037/work/IO/Image/vtkImageWriter.cxx, line 527
vtkPNGWriter (0x2f5dcc0): Ran out of disk space; deleting file(s) already written
And leads to the directory getting garbled with very weird permissions (that require root perms to change/delete) after the error is thrown. The permissions go from
The text was updated successfully, but these errors were encountered:
durack1
changed the title
Cleanup problems attempting to write to directories with rw- (no execute)
Cleanup VTK problems attempting to write to directories with rw- (no execute)
Dec 1, 2017
durack1
changed the title
Cleanup VTK problems attempting to write to directories with rw- (no execute)
VTK problems attempting to write to directories with rw- (no execute)
Dec 1, 2017
I've encountered a nasty error that occurs when target directories do not have execute permissions for the user.
The code below will replicate the issue:
The error is:
And leads to the directory getting garbled with very weird permissions (that require root perms to change/delete) after the error is thrown. The permissions go from
to
@doutriaux1 @danlipsa @aashish24
The text was updated successfully, but these errors were encountered: