[#83096] File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?}) — Nobuyoshi Nakada <nobu@...>
On 2017/10/04 8:47, normal@ruby-lang.org wrote:
5 messages
2017/10/04
[#83100] Re: File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?})
— Eric Wong <normalperson@...>
2017/10/04
Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
[#83105] Re: File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?})
— Nobuyoshi Nakada <nobu@...>
2017/10/04
On 2017/10/04 15:55, Eric Wong wrote:
[#83107] Alias Enumerable#include? to Enumerable#includes? — Alberto Almagro <albertoalmagro@...>
Hello,
9 messages
2017/10/04
[#83113] Re: Alias Enumerable#include? to Enumerable#includes?
— "Urabe, Shyouhei" <shyouhei@...>
2017/10/05
This has been requested countless times, then rejected each and every time.
[#83129] Re: Alias Enumerable#include? to Enumerable#includes?
— Alberto Almagro <albertoalmagro@...>
2017/10/05
Sorry I didn't found it on the core mail list's archive.
[#83138] Re: Alias Enumerable#include? to Enumerable#includes?
— "Urabe, Shyouhei" <shyouhei@...>
2017/10/06
Ruby has not been made of popular votes so far. You have to show us
[#83149] Re: Alias Enumerable#include? to Enumerable#includes?
— Eric Wong <normalperson@...>
2017/10/06
Alberto Almagro <albertoalmagro@gmail.com> wrote:
[#83200] [Ruby trunk Feature#13996] [PATCH] file.c: apply2files releases GVL — normalperson@...
Issue #13996 has been reported by normalperson (Eric Wong).
4 messages
2017/10/10
[ruby-core:83480] Re: [Ruby trunk Feature#7082][Open] Process.kill 0 in windows can return spurious success
From:
RRRoy BBBean <rrroybbbean@...>
Date:
2017-10-21 22:12:43 UTC
List:
ruby-core #83480
Sorry to jump in, but this might help.
In the past, I have had problems with the 'kill' command on Windows 7,
and I stopped using 'kill' on Windows over 4 years ago.
This problem with 'kill' was independent of Ruby. I found that 'kill'
did not (always/sometimes) work from the bash/cygwin command line. No
error. It just didn't work. I figured it was a just a windows thing.
I use the Windows Task Manager on Windows 7 to terminate processes
instead. It always works.
I only mention this because the problem raised may be caused by
underlying software libraries, and not Ruby.
On 10/21/2017 07:02 AM, usa@garbagecollect.jp wrote:
> Issue #7082 has been updated by usa (Usaku NAKAMURA).
>
> Status changed from Assigned to Open
> Assignee deleted (usa (Usaku NAKAMURA))
>
> ----------------------------------------
> Feature #7082: Process.kill 0 in windows can return spurious success
> https://bugs.ruby-lang.org/issues/7082#change-67433
>
> * Author: rogerdpack (Roger Pack)
> * Status: Open
> * Priority: Normal
> * Assignee:
> * Target version: next minor
> ----------------------------------------
>>> a = IO.popen('ls "."', 'w')
> => #<IO:fd 4>
>>> a.pid
> => 2104
>>> Process.kill 0, 2104
> => 1 # should raise an exception since that process is dead now, shouldn't it? [it can be checked with GetExitCodeProcess != STILL_ACTIVE) ?
>
> Thanks!
> -r
>
>
>
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>