Forum: Ruby-core [ruby-trunk - Bug #6715][Open] Dir.mktmpdir fails if you delete it yourself

Issue #6715 has been reported by mitchellh (Mitchell Hashimoto).

----------------------------------------
Bug #6715: Dir.mktmpdir fails if you delete it yourself
https://bugs.ruby-lang.org/issues/6715

Author: mitchellh (Mitchell Hashimoto)
Status: Open
Priority: Normal
Assignee:
Category:
Target version:
ruby -v: 1.9.3-p125


Dir.mktmpdir when given a block will call `FileUtil.remove_entry_secure` 
in the ensure section. If the contents of the block happens to 
move/delete/modify that folder, then that will fail with Errno::ENOENT. 
I believe the correct behavior in this case should be to successfully 
return, since the folder is clearly gone in some way.

2012/7/10 mitchellh (Mitchell Hashimoto) <mitchell.hashimoto@gmail.com>:

> Dir.mktmpdir when given a block will call `FileUtil.remove_entry_secure` in the 
ensure section. If the contents of the block happens to move/delete/modify that 
folder, then that will fail with Errno::ENOENT. I believe the correct behavior in 
this case should be to successfully return, since the folder is clearly gone in 
some way.

I think such application may remove another application's temporary
directory unintentionally.

After you remove the directory, another application may create a
directory with same name.
Then Dir.mktmpdir {} removes that.

If an application itself removes a temporary directory, Dir.mktmpdir
without a block should be used.
It avoids the problem above because Dir.mktmpdir without a block
doesn't remove the directory anyway.

Issue #6715 has been updated by akr (Akira Tanaka).

Status changed from Open to Rejected


----------------------------------------
Bug #6715: Dir.mktmpdir fails if you delete it yourself
https://bugs.ruby-lang.org/issues/6715#change-28078

Author: mitchellh (Mitchell Hashimoto)
Status: Rejected
Priority: Normal
Assignee:
Category:
Target version:
ruby -v: 1.9.3-p125


Dir.mktmpdir when given a block will call `FileUtil.remove_entry_secure` 
in the ensure section. If the contents of the block happens to 
move/delete/modify that folder, then that will fail with Errno::ENOENT. 
I believe the correct behavior in this case should be to successfully 
return, since the folder is clearly gone in some way.