[#64703] Add `Hash#fetch_at` (issue #10017) — Wojtek Mach <wojtek@...>
Hey guys
1 message
2014/09/01
[#64711] [ruby-trunk - Bug #10193] [Closed] TestIO#test_readpartial_locktmp fails randomly — nobu@...
Issue #10193 has been updated by Nobuyoshi Nakada.
3 messages
2014/09/02
[#64744] [ruby-trunk - Bug #10202] [Open] TestBenchmark#test_realtime_output breaks on ARM — v.ondruch@...
Issue #10202 has been reported by Vit Ondruch.
3 messages
2014/09/03
[#64823] documenting constants — Xavier Noria <fxn@...>
I am writing a Rails guide about constant autoloading in Ruby on
5 messages
2014/09/07
[#64838] [ruby-trunk - Bug #10212] [Open] MRI is not for lambda calculus — ko1@...
Issue #10212 has been reported by Koichi Sasada.
6 messages
2014/09/08
[#64858] Re: [ruby-trunk - Bug #10212] [Open] MRI is not for lambda calculus
— Eric Wong <normalperson@...>
2014/09/08
rb_env_t may use a flexible array, helps a little even on my busy system:
[#64871] Re: [ruby-trunk - Bug #10212] [Open] MRI is not for lambda calculus
— SASADA Koichi <ko1@...>
2014/09/08
(2014/09/08 19:48), Eric Wong wrote:
[#64972] [ruby-trunk - Bug #10231] [Open] Process.detach(pid) defines new singleton classes every call — headius@...
Issue #10231 has been reported by Charles Nutter.
3 messages
2014/09/11
[#64980] [ruby-trunk - Bug #10212] MRI is not for lambda calculus — ko1@...
Issue #10212 has been updated by Koichi Sasada.
4 messages
2014/09/12
[#65142] [ruby-trunk - Feature #10267] [Open] Number of processors — akr@...
Issue #10267 has been reported by Akira Tanaka.
4 messages
2014/09/20
[#65144] Re: [ruby-trunk - Feature #10267] [Open] Number of processors
— Eric Wong <normalperson@...>
2014/09/20
akr@fsij.org wrote:
[#65210] [ruby-trunk - misc #10278] [Assigned] [RFC] st.c: use ccan linked list — nobu@...
Issue #10278 has been updated by Nobuyoshi Nakada.
3 messages
2014/09/22
[ruby-core:64724] [ruby-trunk - Feature #10181] New method File.openat()
From:
funny.falcon@...
Date:
2014-09-03 04:58:33 UTC
List:
ruby-core #64724
Issue #10181 has been updated by Yura Sokolov.
If you can reuse result of `opendir(dirname)` why you couldn't reuse result
of `Dir.at(dirname)` ?
29.08.2014 11:55 пользователь "Eric Wong" <normalperson@yhbt.net> написал:
> Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
> > On 08/28/2014 02:53 PM, Eric Wong wrote:
> > >I like this feature.
> > >
> > >If matz approves, I assume you also want to add other *at functions?
> > >e.g. fstatat, renameat, unlinkat, mkdirat, etc.
> >
> > Hm, that suggests...
> >
> > Dir.at(...).open(...)
> > Dir.at(...).fstat(...)
>
> How would that be implemented?
>
> I don't see it working...
>
> The reason for *at functions is the file descriptor points to the
> same file (directory) handle across multiple functions; in other words
> it's a way to avoid race conditions by creating a private reference
> to a container object (an FS directory)
>
> The file descriptor points to the same directory regardless of whether
> it's renamed (moved) or not.
>
> One can think of FS operations as operations on Ruby hashes.
> In your example, it might be like the following, assuming
> "fs" is a giant hash protected by OS-wide locks:
>
> # Dir.at(dirname).open("foo")
> fs[dirname]["foo"] # open("/dirname/foo", ...)
> # another thread may replace/remove
> # root[dirname] here
> # Dir.at(dirname).open("bar")
> fs[dirname]["bar"] # open("/dirname/bar", ...)
>
> We cannot guarantee Dir.at(dirname) / fs[dirname] returns
> the same value twice when called in succession.
>
> openat lets you work like this:
>
> dh = fs[dirname] # dh = opendir(dirname)
> dh["foo"] # openat(fileno(dh), "foo", ...)
> dh["bar"] # openat(fileno(dh), "bar", ...)
> ...
>
> Other threads can remove/replace/rename fs[dirname] with another
> directory, but the directory handle from the initial lookup
> remains valid to the thread which opened it.
>
----------------------------------------
Feature #10181: New method File.openat()
https://bugs.ruby-lang.org/issues/10181#change-48620
* Author: Technorama Ltd.
* Status: Open
* Priority: Normal
* Assignee:
* Category:
* Target version:
----------------------------------------
The purpose of the openat() function is to enable opening files in directories other than the current working directory without exposure to race conditions. Any part of the path of a file could be changed in parallel to a call to open(), resulting in unspecified behavior. By opening a file descriptor for the target directory and using the openat() function it can be guaranteed that the opened file is located relative to the desired directory.
openat() is part of POSIX.1-2008.
Compatibility:
Linux kernel >= 2.6.16
FreeBSD >= 7.0
OpenBSD >= 5.0
NetBSD >= 6.1.4
MacOS/X no
Pull request: https://github.com/ruby/ruby/pull/706
--
https://bugs.ruby-lang.org/