[#79914] [Ruby trunk Bug#13282] opt_str_freeze does not always dedupe — normalperson@...
Issue #13282 has been reported by Eric Wong.
4 messages
2017/03/05
[#80140] [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus) — shyouhei@...
Issue #13295 has been updated by shyouhei (Shyouhei Urabe).
5 messages
2017/03/13
[#80362] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— Eric Wong <normalperson@...>
2017/03/26
shyouhei@ruby-lang.org wrote:
[#80368] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— SASADA Koichi <ko1@...>
2017/03/27
On 2017/03/26 15:16, Eric Wong wrote:
[#80205] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint — Eric Wong <normalperson@...>
duerst@ruby-lang.org wrote:
4 messages
2017/03/17
[#80213] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint
— Martin J. Dürst <duerst@...>
2017/03/17
Hello Eric,
[#80290] [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch — normalperson@...
Issue #13355 has been reported by normalperson (Eric Wong).
4 messages
2017/03/23
[#80410] Re: [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch
— Eric Wong <normalperson@...>
2017/03/27
normalperson@yhbt.net wrote:
[#80415] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
5 messages
2017/03/28
[#80488] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
4 messages
2017/03/29
[ruby-core:80475] [Ruby trunk Feature#12410][Rejected] Process.uid= validation and casting
From:
naruse@...
Date:
2017-03-29 10:02:38 UTC
List:
ruby-core #80475
Issue #12410 has been updated by naruse (Yui NARUSE).
Status changed from Open to Rejected
As follows, it looks because BSD id(1) handles the uid argument as 32bit integer.
(Note that GNU coreutils' id(1) doesn't allow negative argument)
```sh
% id -un -- -4294967296
root
```
Therefore this behavior is considered as unexpected behavior and Ruby shouldn't follow it.
----------------------------------------
Feature #12410: Process.uid= validation and casting
https://bugs.ruby-lang.org/issues/12410#change-63971
* Author: djberg96 (Daniel Berger)
* Status: Rejected
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
OSX 10.11.4
Ruby 2.2.x and 2.3.x
It seems that Ruby added the ability to use a string for Process.uid, which is nice. But, it has introduced inconsistency with regards to enforcement:
> Process.uid = 'bogus' # ArgumentError: can't find user for bogus
> Process.uid = 999999 # Does not raise an error, even though the uid is invalid
Also, it seems there's some sort of casting bug for negative values:
> Process.uid = -1 # -1
> Process.uid # 0
> Process.uid = -2 # -2
> Process.uid # 4294967294
While this is almost certainly an issue with the underlying C function (somewhat concerning), I think we should validate the values passed to `Process.uid=` (and similar methods) the same way we validate it for the string. Presumably a simple `getpwuid` check would work.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>