Activity
From 01/21/2014 to 01/27/2014
01/27/2014
-
11:56 PM Bug #9455 (Closed): Blocks do not round-trip properly through ISeq dump/load - Applied in changeset r44720.
----------
compile.c: use correct key for block when loading serialized iseqs
* compile.c (iseq_build_from_ary_body): Use :blockptr instead of :block
as hash key when loading serialized instruction sequen... - 11:50 PM Bug #9455 (Closed): Blocks do not round-trip properly through ISeq dump/load
- Blocks passed to methods do not round-trip properly when dumped with RubyVM::InstructionSequence#to_a and then loaded again with rb_iseq_load.
This is because iseq_data_to_ary in iseq.c stores serialized blocks under the :blockptr key... - 11:56 PM Revision d248a2c9 (git): * 2014-01-28
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44721 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 11:56 PM Revision a22dd11a (git): compile.c: use correct key for block when loading serialized iseqs
- * compile.c (iseq_build_from_ary_body): Use :blockptr instead of :block
as hash key when loading serialized instruction sequences from arrays.
[Bug #9455] [ruby-core:60146]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44720 b2d... -
11:41 PM Bug #9262: global_method_cache should be configurable or grow automatically
- SASADA Koichi <ko1@atdot.net> wrote:
> From Ruby 2.0, we use inline/global method cache aggressively. So
> performance impact on method cache miss has huge impact (compare with
> Ruby 1.8, 1.9), that guys already show.
Not a serio... -
10:51 PM Bug #9437: Build of ruby 2.1.0 fails on AIX 6.1
- Yutaka Kanemoto wrote:
> Since we are not able to remove `-L.` at this point, ...
Why do we need -L. ?
(I'm not arguing that we don't. I just don't understand why we do.)
-
- Here are my thoughts. First, create a script shown below. I call the script get-path
#!/usr/bin/sh
echo 'int main() { return 0; }' > temp.c
gcc -o temp temp.c
for i in ` dump -H temp | awk '$1 == "0" {print ... -
- I have verified that the article mentioned above is correct (I've reproduced it). I am continuing on with trying to find a solution.
-
- I believe (rather strongly) that the ssh report is incorrect. I recall a test deep inside the loader that does not load libraries under dangerous conditions. I recall seeing this flaw myself but when I tried to take advantage of it, I ...
-
06:07 AM Bug #9437: Build of ruby 2.1.0 fails on AIX 6.1
- Thank you for the clarification.
Then should we enumerate all directories for other libraries, not only `gmp`? -
04:11 AM Bug #9437: Build of ruby 2.1.0 fails on AIX 6.1
- Hi,
This is AIX's `ld`'s behavior:
----
from man ld
```
-LDirectory
Adds Directory to the list of search directories used for finding libraries designated by the -l
(lowercase letter L) flag. T... -
- As far as which -L option is causing the issue, I don't know. Most open source programs do not set libpath as Ruby is doing. Why Ruby is doing it is somewhere in the history of Ruby's discussions I would assume. su will work without s...
-
- Perry Smith wrote:
> I think the -L option that it producing the angst is "-L.". I wonder if it might be easiest to somehow remove that option.
Could you confirm it?
I have no AIX environments.
> ...
Although I can't remember ... -
- This option
-Wl,-blibpath:/gsa/ausgsa/projects/r/ruby/prvm/ruby-2.1.0/lib:/usr/lib:/lib
sets the libpath inside the executable. "dump -H miniruby" will show
/gsa/ausgsa/projects/r/ruby/prvm/ruby-2.1.0/lib:/usr/lib:/lib
... -
10:35 PM Feature #3333: mkmf (have|find)_cxx_header
- could I request an update on this please?
-
06:59 PM Revision f48ae0d1 (git): merge revision(s) 44717:
- * configure.in: define USE_BUILTIN_FRAME_ADDRESS on x86_64
even if __builtin_frame_address is not used now.
By this, FreeBSD's clang can build ruby 1.8,
and alloca(1) doesn't work on it.
git-svn-id: svn+ss... - 06:58 PM Revision 50783b87 (git): * 2014-01-28
- git-svn-id: svn+ssh://svn.ruby-lang.org/ruby/branches/ruby_1_8@44718 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- even if __builtin_frame_address is not used now.
By this, FreeBSD's clang can build ruby 1.8,
and alloca(1) doesn't work on it.
git-svn-id: svn+ssh://svn.ruby-lang.org/ruby/branches/ruby_1_8@44717 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:09 PM Bug #9384: Segfault in ruby 2.1.0p0
- Ok, thank you for your help
-
01:35 PM Revision 418608fe (git): * ChangeLog: remove a duplicated entry at r44712.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44716 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * thread_pthread.c (ruby_stack_overflowed_p): range of rlim_cur
may be larger than size_t. [ruby-core:60113] [Bug #9454]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44715 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * signal.c (sigsegv): make message string static to suppress
unnecessary copy.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44714 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Applied in changeset r44712.
----------
thread_pthread.c: get current main thread stack size
* thread_pthread.c: get current main thread stack size, which may
be expanded than allocated size at initialization, by rlimit().
[ruby-co... -
- At first glan.ce, it occurred in `INSNS_DISPATCH()` macro.
Considering that the second case works fine, maybe recovery jump fails.
-
12:31 AM Bug #9454: The define_method(:class) segfault
- Sure. As far as I understand it should raise a *SystemStackError* instead of segfaulting (that's how it worked before *v2.1.0p0*). If you could give me a hint, which file is relevant, I would probably come up with a patch (I don't promis...
- 12:53 PM Revision 1c391063 (git): * 2014-01-27
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44713 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * thread_pthread.c: get current main thread stack size, which may
be expanded than allocated size at initialization, by rlimit().
[ruby-core:60113] [Bug #9454]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44712 b2dd03c8-39d4-4d... -
- * ext/bigdecimal/bigdecimal.c (BigDecimal_divide): Add an additional
digit for the quotient to be compatible with bigdecimal 1.2.1 and
the former. [ruby-core:59365] [#9316] [#9305]
* test/bigdecimal/test_big... -
07:56 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Just wanted to tell @emboss that (step aside from my position here)
the patch he proposed itself seems adequate for the purpose. 0.9.8
with zlib provies no way to disable compression so you cannot save
that case anyway.
My seeing ... -
05:51 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- shyouhei@ruby-lang.org wrote:
>
> Alright, I see you are not blaming Debian people. Thank you.
>
> But I see "I don't know what these lines of code in OpenSSL do, but Valgrind
> complains." is a completely valid reason to fix som... -
03:44 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Martin Bosslet wrote:
> a) I want to apologize for overlooking this
Ah, you don't need to apologize at all! I just wanted to clarify what is relieved and what is not.
> ...
Me too, but I'm curious about the reason why OpenSSL p... -
- Sam Gleske wrote:
> Take a leaf out of Apache's book. Give sane defaults (or use OpenSSL) but give users a way to configure ciphers.
> ...
I can't understand your point at all. Please elaborate.
According to the URL you gave, Apac... -
01:47 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Yusuke Endoh wrote:
> Cooperatively with some committers, I investigated the current condition of default settings in OpenSSL (and OS X). It is very complicated. Correct me if I'm wrong.
Thanks for that!
> ...
That's the kind of... -
- * ext/openssl/ossl_ssl.c (Init_ossl_ssl): Declare a constant
`OP_MSIE_SSLV2_RSA_PADDING` only if the macro is defined. The
`SSL_OP_MSIE_SSLV2_RSA_PADDING` has been removed from latest
snapshot of OpenSSL 1.... -
- :+1: nice-to-have. Also agree that #options= is too vague in name.
-
- e@zzak.io wrote:
> Sorry I haven't had time to commit this since you submitted it 8 days ago.
No worries.
> Please commit your patch, send matz@ruby-lang.org an email requesting commit.
>
> Also, please take notice of Bug #925... -
- Aaron Patterson wrote:
> On Sat, Jan 25, 2014 at 12:32:12AM +0000, mame@tsg.ne.jp wrote:
> ...
No, not at all :)
> > Shyouhei's point is that we can no longer develop the OpenSSL extension.
> ...
Those who know me also know that ...
01/26/2014
-
- Seems an infinite recursion, obviously.
-
- Here's the log with the segfault.
-
- Ruby 2.1.0p0 segfaults when I invoke the following code.
define_method(:class) { self.class }
self.class #=> segfault :(
It affects exclusively Ruby 2.1.0p0 (I also tested on the most recent 2.0.0, 1.9.3 and 1.8.7).
By ... -
10:19 PM Feature #9439: Remove OpenSSL from stdlib
- This seems ok so long as Digest is still available and RubyGems pins to particular builds of OpenSSL via a hash. That way RubyGems could download a known good OpenSSL over plaintext HTTP and check its hash to know it got the copy it's ex...
-
05:55 PM Feature #9453 (Rejected): Return symbols of defined methods for `attr` and friends
- With Ruby 2.1 returning a symbol from `def` and `define_method`, that leaves `attr`, `attr_reader`, `attr_writer`, and `attr_accessor` as ways to define methods that still return nil. This is unfortunate, because it prevents the use of m...
-
03:01 PM Bug #9452 (Closed): Refining methods that should be private
- Are refinements also meant to add private methods? This is what I tried:
module R
refine Object do
def m
puts "Success!"
end
private(:m)
end
end
using R
m # ... -
- Sam Gleske wrote:
> Take a leaf out of Apache's book. Give sane defaults (or use OpenSSL) but give users a way to configure ciphers.
> ...
Why you can't say that to OpenSSL people?
Is it because you think it is easier to trample do... -
06:48 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Take a leaf out of Apache's book. Give sane defaults (or use OpenSSL) but give users a way to configure ciphers.
http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslciphersuite -
- Not sure if this is a bug or feature request:
~~~ruby
require 'minitest/autorun'
require 'set'
module ClassToProc
refine Class do
def to_proc
lambda{ |*args| self.new(*args) }
end
end
end
using ClassToP... -
01:13 PM Feature #9450 (Closed): Allow overriding SSLContext options in Net::HTTP
- While the Ruby team is hashing out the future of OpenSSL in Ruby, I thought it would be useful to add the missing hook so that end-users could control their behavior when issuing HTTP requests.
Right now it's possible to specific a sp... -
- I tried jemalloc 3.5.0 vs eglibc 2.13-38 (Debian x86_64)
http://80x24.org/bmlog-20140126-003136.7320.gz
Mostly close results, but I think our "make benchmark" suite is
incomplete and we need more fork/concurrency-intensive benchm... -
- nobu@ruby-lang.org wrote:
> Is it an issue of the test code?
>
> http://c5664.rubyci.org/~chkbuild/ruby-trunk/log/20140125T233302Z.log.html.gz
Odd, I did not get this:
10) Error:
TestProcess#test_deadlock_by_signal_at_forkin... -
- Is it an issue of the test code?
http://c5664.rubyci.org/~chkbuild/ruby-trunk/log/20140125T233302Z.log.html.gz
01/25/2014
- 11:42 PM Revision 4f63c763 (git): * 2014-01-26
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44709 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * localeinit.c (SIZEOF_CP_NAME, CP_FORMAT): needed on cygwin too.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44708 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
10:53 PM Bug #9337: [BUG] Segmentation fault at 0x00000000000018 ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-linux]
- I also get this error, while running ruby 2.1.0 on my rails app, iMac, trying to run my first rspec test.
-
01:33 PM Bug #9448: Assignment with overridden []= returns return value of method rather than new value
- Thanks a lot for the quick fix!
-
- nobu@ruby-lang.org wrote:
> Applied in changeset r44705.
Thank you! Sorry for the breakage.
I need to study/understand compile.c better :x -
- Applied in changeset r44705.
----------
compile.c: assignment result of aset_with
* compile.c (iseq_compile_each): result of assignment should be
its rhs instead of returned value from a method.
[ruby-core:60071] [Bug #9448] -
- normalperson@yhbt.net wrote:
> I think you misread, he is saying assignment returns the value returned
> by the method in trunk. It looks like trunk is violating spec.
> I think it is r44551, opt_aset_str causing the bug. Fix co... -
- Indeed, thank you.
-
- nobu@ruby-lang.org wrote:
> Status changed from Open to Rejected
>
> It's a spec.
> An assignment returns the assigned value, not the value returned by the method.
I think you misread, he is saying assignment returns the value r... -
- It's a spec.
An assignment returns the assigned value, not the value returned by the method. -
01:18 PM Revision 536037e7 (git): * README.ja.md, README.md: update the controller address of mailing lists.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44707 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- nobu@ruby-lang.org wrote:
> Oops, I missed to include the reference in r44706.
No worries. Interesting, now I notice test_process now fails under
heavy load with this patch...
This should fix things: http://bogomips.org/ruby.gi... -
- Oops, I missed to include the reference in r44706.
-
- Perry Smith wrote:
> But the compile line tells ld to ignore the -L flags when it creates the final executable and make the libpath be /gsa/ausgsa/projects/r/ruby/prvm/ruby-2.1.0/lib:/usr/lib:/lib Now, the executable depends upon thing... -
- miniruby is built with a command that looks like this:
gcc -O3 -fno-fast-math -ggdb3 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -Wno-long-long -Wno-missing-field-initializers -Wunused-variable -Wpointer-arith -Wwrite-str... -
- My point is OpenSSL extension shall not be maintained by ruby-core any longer. OpenSSL itself is useful. The thing is the fact that we are maintaining that extension, is greatly prejudicing its value. It does not benefit anyone.
So... -
02:12 AM Feature #9439: Remove OpenSSL from stdlib
- On Sat, Jan 25, 2014 at 12:32:12AM +0000, mame@tsg.ne.jp wrote:
> Issue #9439 has been updated by Yusuke Endoh.
>
>
> Aaron Patterson wrote:
> > Can we take a less extreme approach? We should convert openssl to a gem
> > that... -
- Aaron Patterson wrote:
> Can we take a less extreme approach? We should convert openssl to a gem
> ...
Then, who will maintain the OpenSSL gem?
Shyouhei's point is that we can no longer develop the OpenSSL extension.
Just convertin... -
- B Kelly wrote:
> > Thus, I do not trust such "kind" words. True contributors do never say "I
> ...
(Sorry I'm unsure which blacklisting and whitelisting is better, but in general) I think reviewing a patch is a valuable contribution... - 06:52 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Shyouhei Urabe wrote:
> I can settle for compromise to introduce the proposed patch if everyone agrees to give up requesting ruby to be secure by default; it HAPPEN TO become what you call secure and that's not a future-guaranteed statu... -
- I can settle for compromise to introduce the proposed patch if everyone agrees to give up requesting ruby to be secure by default; it HAPPEN TO become what you call secure and that's not a future-guaranteed status. The devs are not goin...
-
- B Kelly wrote:
> Interesting. I feel I must be communicating unclearly.
> ...
Alright, I see you are not blaming Debian people. Thank you.
But I see "I don't know what these lines of code in OpenSSL do, but Valgrind
complains." ... -
- * process.c (send_child_error): retry write on EINTR to fix
occasional Errno::EINTR from Process.spawn.
* process.c (recv_child_error): retry read on EINTR to fix
occasional Errno::EINTR from Process.spawn.
git-svn-id: svn+ssh://ci.... -
- * compile.c (iseq_compile_each): result of assignment should be
its rhs instead of returned value from a method.
[ruby-core:60071] [Bug #9448]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44705 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * compile.c (iseq_compile_each): fstring is need marking.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44704 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * insns.def (opt_mod, opt_aset_with, opt_aref_with, opt_regexpmatch1):
adjust style, do not cuddle else up.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44703 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * class.c (rb_extract_keywords): treat nil keyword_hash same as 0,
for the case rb_scan_args returns nil if no keyword hash.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44702 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 01:55 AM Revision 6a634322 (git): * 2014-01-25
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44701 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * class.c (rb_obj_methods): simplify without jump.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44700 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
01/24/2014
-
- On Fri, Jan 24, 2014 at 09:05:18PM +0000, usa@garbagecollect.jp wrote:
> Issue #9439 has been updated by Usaku NAKAMURA.
>
>
> I would like to clarify the problem.
>
> As already stated, RubyGems uses OpenSSL.
> To say strictl... -
09:05 PM Feature #9439: Remove OpenSSL from stdlib
- I would like to clarify the problem.
As already stated, RubyGems uses OpenSSL.
To say strictly, RubyGems uses OpenSSL for https, signing, and its verification.
Therefore, the option which we can take is as follows:
(1) Maintain the... -
- mame@tsg.ne.jp wrote:
>
> Off-topic: A bigger problem is "kind" people. In an extreme case, we can
> ignore those who just require something. But it is far more difficult to
> ignore those who kindly say "I can help you." In fac... -
- Shyouhei Urabe wrote:
> OpenSSL seemd easy to support at first. We were only needed to
> ...
Fully agreed. That said, I'm not positive for the proposal as long as Martin Bosslet is willing to maintain the library.
Off-topic: A b... -
05:33 AM Feature #9439: Remove OpenSSL from stdlib
- Just like to point out that unless the indexes and metadata exposed by api.rubygems.org is somehow cryptographically signed, an attacker can MITM rubygems.org and tell clients that rails version 9000 is available for updating.
-
- Fabian Ruff wrote:
> I must be missing something here but I feel like I'm going crazy over this.
> ...
Yes. I have to admit that ruby devs, especially myself, are not
ready. Immature to support OpenSSL.
OpenSSL seemd easy to supp... -
- It looks like r44687 implements a partial fix for this, but my
proposed patch covers more cases and is more complete.
* process.c (recv_child_error): Fix deadlock in rb_fork_internal when a
signal is sent to the parent proc... -
11:11 PM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Why do people think it's impossible to disable TLS compression on 0.9.8 with zlib installed?
-
07:55 PM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- First of all thanks to Martin for working on the white list. I still believe specifying defaults here is the best of bad choices to make.
Regarding defaults on OS X, tools like RVM, rbenv and chruby are used a lot. All either build O... -
- Cooperatively with some committers, I investigated the current condition of default settings in OpenSSL (and OS X). It is very complicated. Correct me if I'm wrong.
Summary:
* [IMPORTANT] Emboss's patch does NOT always work. The... -
- Yuki Izumi wrote:
> Shyouhei Urabe wrote:
> ...
Maybe not, because I wasn't intend to attack women (but you replied
like this). Sorry about this. I don't know how to express this
situation then. Very depressed.
-
- shyouhei@ruby-lang.org wrote:
> B Kelly wrote:
>>
>> I think we're talking at cross-purposes. Your arguments focus on what would
>> be ideal: an upstream patch by OpenSSL. I think nobody disagrees that would be
>> ideal, and... -
03:25 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Shyouhei Urabe wrote:
> I don't wanna be raped like them.
How on earth can you think this is appropriate? -
- B Kelly wrote:
> Martin.Bosslet@gmail.com wrote:
> ...
Then how can it be legitimate for you to blame Debian people?
I don't wanna be raped like them.
> >> > It hurts even more that in such cases everyone will start pointing fing... -
- When calling []= the assignment will return the return value of the []= method, rather than the value of the right-hand side, which is the behaviour in 2.1.0-p0, 2.0.0-p353 and 1.9.3-p484.
Example code:
class Animal ... -
09:19 PM Feature #6373: public #self
- > Mmm, no, that's quite different. `"".presence # => nil` for example.
Yes, I was aware of the differences from ActiveSupport presence, I just wanted to point out the similar need for chaining "`itself`" with a block.
The proposed ... -
05:57 PM Bug #9447: Bad interaction between Fibers and Trap handlers in Ruby > 2.0.0
- Just a clarification, the issue is that:
Alarm.alarm(timeout_seconds) do
# potentially time consuming operation which must have a timeout
end
# when a timeout occurs, this code will still be in trap context
# so th... -
- Hi there,
I've been using and Alarm class I created, which gives Ruby code access to the alarm system call.
It used to work perfectly on 1.9.3 with no issues and more than 1 year of production usage.
Ruby 2.0.0 doesn't let me use ... -
05:41 PM Bug #9285: Exception message of Errno::ENOENT contains strings @ rb_sysopen and @ dir_initialize in Ruby 2.1
- I don't like just turning hidden because I can't agree release build doesn't need debug.
But I agree current format is a little confusable and C function name is less important.
String format could be improved if someone propose bette... -
03:43 PM Misc #9446 (Closed): DRb documentation should notice that start_service should be called at least once per process
- Please take a look at my PR in GitHub for more details:
https://github.com/ruby/ruby/pull/514
I forgot to mention there that we're still using Ruby 2.0.0-p353 as I can't compile 2.1.0 on Debian sid. -
01:48 PM Bug #9444 (Closed): Segmentation fault in vendor/bundle/gems/json-1.8.1/lib/json/common.rb:67: [BUG]
- Chris Seng wrote:
> Output from that command:
> ...
(snip)
>
> ...
You need to cleanup vendor/bundle folder(like rm -r) and bundle install. -
12:42 PM Bug #9444: Segmentation fault in vendor/bundle/gems/json-1.8.1/lib/json/common.rb:67: [BUG]
- Output from that command:
linux-vdso.so.1 => (0x00007fff85ffe000)
libruby-1.9.1.so.1.9 => /usr/lib/libruby-1.9.1.so.1.9 (0x00007f47b2f76000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f47b2bae000)
libpthread.so.0 => ... -
- Try `ldd /home/seng/programming/cpd/vendor/bundle/gems/json-1.8.1/lib/json/ext/generator.so`.
-
- * vm_backtrace.c (rb_backtrace_print_as_bugreport): initialize
header-printed flag.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44699 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * test/ruby/test_process.rb (test_clock_getres): ignore if
clock_getres is no supported, e.g., on old Linux.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44698 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:15 AM Bug #9429 (Closed): Fix typos
- Applied in changeset r44696.
----------
* lib/racc/rdoc/grammar.en.rdoc: [DOC] Correct grammar and typos
Patch by Giorgos Tsiftsis [Bug #9429] [ci skip] - 06:15 AM Revision 21655532 (git): * 2014-01-24
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44697 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Patch by Giorgos Tsiftsis [Bug #9429] [ci skip]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44696 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:01 AM Feature #9445: Support emitting 1.9 Symbol keyword Hash syntax when pretty printing Hashes
- I think it's better to not add unnecessary complexity. After all, we don't represent strings with single quotes, even when they don't contain escaped characters, and even when they *do* contain double-quote characters.
-
- While it may not be pretty, it is still valid Ruby syntax. If others disagree with mixing the two syntaxes, I can adjust the patch.
-
- Mixing `foo:` and `bar =>` doesn't seem pretty to me.
-
- Ruby 1.9 first introduced support for keyword Hash syntax for simple Symbol keys. However, Hash#inspect and pp do not emit the same syntax when printing Symbol keys. This patch adds support for "foo: " syntax to the pp_hash method, iff t...
-
- (I'm totally neutral about this particular patch but) I like Eric's
patches very much in general. They are fairly well written, well
commented. I'm strongly +1 to add him our team. -
-
- Hello Eric!
Sorry I haven't had time to commit this since you submitted it 8 days ago.
Please commit your patch, send matz@ruby-lang.org an email requesting commit.
Also, please take notice of Bug #9254. Some other notes to add ...
01/23/2014
-
- Martin.Bosslet@gmail.com wrote:
>
> B Kelly wrote:
>>
>> The Debian maintainer _removed lines of code_ from the OpenSSL PRNG
>> implementation. [1]
>>
>> This is hardly in the same category as tightening the defaults to ... -
- Yusuke Endoh wrote:
>
> ...
Np, thank you!
B Kelly wrote:
> Martin.Bosslet@gmail.com wrote:
> ...
And it is. It doesn't matter if you remove something or if you think (!) you are improving the situation. The final patch we all a... -
- Martin.Bosslet@gmail.com wrote:
>
> Rolling your own defaults is dangerous: Even skilled developers like the
> Debian developers can get it wrong sometimes, with disastrous consequences.
The Debian blunder has been referenced twic... -
- I updated to 2.0.0 via RVM for a Rails 4.0.0 project and received the error below upon running a rake task. I am too much of a novice to identify the cause based on the message below, but the instructions indicated that I should report ...
-
10:27 PM Feature #9423: Improve warning semantics
- What we need are structured warnings, not a warning level system.
https://github.com/schmidt/structured_warnings
http://www.oreillynet.com/ruby/blog/2008/02/structured_warnings_now.html -
- normalperson@yhbt.net wrote:
> misc #9421: [PATCH] doc/contributing.rdoc: allow/encourage other git hosts
> https://bugs.ruby-lang.org/issues/9421
>
> git is a distributed system, so make it clear to potential contributors
> that ... -
06:23 PM Bug #9443 (Rejected): Prepended methods are skipped if calling alias
- I am unsure if this is related to https://bugs.ruby-lang.org/issues/7842 as that issue specifically mentions the user of "super" which my example code does not use. Anyway, here is the test to recreate:
```ruby
require 'test/unit'
... -
- Eric Hodel wrote:
> I'm not informed of the details of how TUF works, but the implementation in progress uses OpenSSL to verify metadata and packages, so Ruby will still require OpenSSL.
Yes, TUF uses the RSASSA PKCS#1v1.5 digital si... -
- Em 22-01-2014 21:38, sam@kottlerdevelopment.com escreveu:
> Issue #9439 has been updated by Sam Kottler.
>
>
> Rodrigo Rosenfeld Rosas wrote:
>> Em 22-01-2014 16:39, luislavena@gmail.com escreveu:
>> > Issue #9439 has been updat... -
10:18 AM Feature #9439: Remove OpenSSL from stdlib
- I must be missing something here but I feel like I'm going crazy over this.
Are we really talking about removing the capability for https communication from ruby core while the world is shifting towards https-only?
To me this is bigg... -
- Forget GPG if you guys don't like it; it's just an alternative.
I had a really rough glance at the TUF pull request and it seems
OpenSSL is used only for SHA and RSA algorithms and not for the
secure socket layer. We can find adequ... -
- Sam Kottler wrote:
> Shyouhei Urabe wrote:
> ...
RubyGems can include its public key in its canonical distribution.
Regardless of their doing so or not, never use a ruby source code
that you cannot trust. Including public key(s) in ... -
04:03 PM Feature #9442: Multiple comparison construction with `==` and `===`
- Yukihiro Matsumoto wrote:
> I am sorry but the proposed syntax conflicts with the existing syntax, especially the equal operator one.
> ...
My understanding is that
a, b == 1, 2
or
1, 2 === a, b
among which I am not... -
- I think that it is better to optimize the specific form of case statements than to introduce a new syntax.
--
Yusuke Endoh <mame@tsg.ne.jp> -
12:16 PM Feature #9442 (Rejected): Multiple comparison construction with `==` and `===`
- I am sorry but the proposed syntax conflicts with the existing syntax, especially the equal operator one.
You have proposed improvement on case statement, but it still conflicts.
So (until someone come up with the new non-conflicting... -
- The conventional `case` construction allows alternatives to be separated with a comma:
case a
when 1, 2, 3, 4 then ...
when 5 then ...
...
In order to resolve ambiguity/confusion, parentheses may be used when mul... -
- I often want to write a condition that depends on multiple variables like this:
if a == 1 and b == 2 then ...
elsif a == 2 and b == 1 then ...
elsif a == 2 and b == 2 then ...
...
In order to make this compact, I... -
- * vm_insnhelper.c (check_match): Fix SEGV with VM_CHECKMATCH_TYPE_CASE
and class of `pattern` has `method_missing`
[Bug #8882] [ruby-core:58606]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_0_0@44695 ... -
11:22 AM Revision 37f32fd6 (git): * test/ruby/envutil.rb: try to wait a bit (0.1sec) when ruby process
- exits by signals because some SEGV tests fail because of not enough
error output.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44694 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44693 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44692 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * test/ruby/test_process.rb (test_deadlock_by_signal_at_forking):
fix condition to define.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44691 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * lib/test/unit/assertions.rb (assert_raise): allow a proc as
message like as other assertions.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44690 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * test/ruby/test_process.rb (test_deadlock_by_signal_at_forking): test
for r44687, deadlock in rb_fork_internal().
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44689 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- What's your platform?
-
- After updated again, I see that `make runnable` created a bin/ruby symlink. However, --enable-shared requires that LD_LIBRARY_PATH=./lib/ is set. Also, bin/ruby cannot find core libraries such as 'thread'.
-
- Applied in changeset r44688.
----------
* lib/fileutils.rb: [DOC] Fix typo in options_of() example [Bug #9392]
Patch by Giorgos Tsiftsis -
- Patch by Giorgos Tsiftsis
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44688 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- This was fixed by Matsuda-san in r44121
- 05:07 AM Revision 0a881f81 (git): * process.c (recv_child_error): Fix deadlock in rb_fork_internal when a
- signal is sent to the parent process while Ruby is forking in IO.popen.
Patch by Scott Francis. Closes GH-513.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44687 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 04:59 AM Feature #9441 (Closed): [PATCH] method.h: save 8 bytes in rb_method_definition_t on x86-64
- Applied in changeset r44686.
----------
* method.h: rearrange rb_method_definition_struct to save 8 bytes in
padding on 64 bit platforms. Patch by Eric Wong.
[Feature #9441] [ruby-core:59993] -
- Applied in changeset r44684.
----------
* README -> README.md: [DOC] Format README with Markdown [Bug #9255]
* README.ja -> README.ja.md: ditto - 04:59 AM Revision 25daaafa (git): * method.h: rearrange rb_method_definition_struct to save 8 bytes in
- padding on 64 bit platforms. Patch by Eric Wong.
[Feature #9441] [ruby-core:59993]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44686 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 04:59 AM Revision 3aeff611 (git): * 2014-01-23
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44685 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * README.ja -> README.ja.md: ditto
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44684 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I concur with Charlie Somerville. It does seem asymetrical that there is a `__FILE__` constant, but no `__file__` method.
-
- Tested against r44682 on bash 4.2.5 and got the same error:
$ ./configure --prefix="$HOME/foo bar"
$ make
...
linking static-library libruby-static.a
verifying static-library libruby-static.a
linking ruby
... -
- hash.c: reword
* hash.c (HAS_EXTRA_STATES, rb_hash_reject): use words "extra states".
* hash.c (HAS_EXTRA_STATES): warn extra states only when something
differ. [ruby-core:59254] [Bug #9275]
git-svn-id: svn+... -
- Unless we have use for it, I don't think rb_io_writev should be in
the C API, and even less reason for it to be public for extensions
in ruby/intern.h
Also, it'd probably be good to dedup the fptr->wbuf initialization
code in io_b...
01/22/2014
-
11:41 PM Feature #9439: Remove OpenSSL from stdlib
- Shyouhei Urabe wrote:
> > All what gem need is the digital sigunature.
> ...
Not really. GPG implementations are platform specific and require a higher level of end-user involvement than just plain SSL. Additionally, we need a way to h... -
- Rodrigo Rosenfeld Rosas wrote:
> Em 22-01-2014 16:39, luislavena@gmail.com escreveu:
> ...
I'm one of the maintainers of rubygems.org and bundler and haven't ever heard this complaint before. Can you email me with more info about your ... -
- Em 22-01-2014 16:39, luislavena@gmail.com escreveu:
> Issue #9439 has been updated by Luis Lavena.
>
>
> Shyouhei Urabe wrote:
>> Very true. I have no idea on why RubyGems use https and not other tools. Any pointers?
> AFAIK is ... -
09:28 PM Feature #9439: Remove OpenSSL from stdlib
- I'm not informed of the details of how TUF works, but the implementation in progress uses OpenSSL to verify metadata and packages, so Ruby will still require OpenSSL.
RubyGems already supports signing gems using OpenSSL, but there are... -
06:39 PM Feature #9439: Remove OpenSSL from stdlib
- Shyouhei Urabe wrote:
>
> ...
AFAIK is to avoid MITM attacks and such, since if signatures are also stored along packages, how can you verify that the packages are not altered?
You will say why RubyGems don't use something else, we... -
- Luis Lavena wrote:
> Shyouhei Urabe wrote:
> ...
Very true. I have no idea on why RubyGems use https and not other tools. Any pointers? -
- Shyouhei Urabe wrote:
> > All what gem need is the digital sigunature.
> ...
That means gpg becomes an external dependency of the build/integration process.
gpg is not available in all the platforms.
There has been a bunch of res... -
- > All what gem need is the digital sigunature.
To be precise it only needs to verify signatures. Signing itself can be done using other tools, like gpg(1).
-
- Why must RubyGems use https? Shouldn't it suffice to check the sanity of downloaded packages?
I mean, can't we live without the secure socket? All what gem need is the digital sigunature. -
- Yui NARUSE wrote:
> There are some ways for example use package manager of the OS or a browser or curl or something and download openssl.gem.
> ...
If it is right, don't we have the necessity of bundling rubygems itself any longer? -
- Charlie Somerville wrote:
> How will RubyGems use HTTPS without OpenSSL?
Good point.
This proposal should include the answer of this issue.
There are some ways for example use package manager of the OS or a browser or curl or som... - 03:59 AM Feature #9439: Remove OpenSSL from stdlib
- How will RubyGems use HTTPS without OpenSSL?
-
- :+1:
Nursing OpenSSL's being bad is beyond our power. -
- See also #9424
-
- Regarding [ruby-core:59943], I agree with nobu that we should remove OpenSSL from ruby.
It's become too hard to maintain, and would better serve our users to encourage the use of a different implementation.
Another benefit of remov... -
- Btw, jemalloc 3.5 includes an updated non-standard experimental API.
It looks like it has the ability to specify different arenas for
allocation (via MALLOCX_ARENA(a)). Perhaps could be used to
distinguish long/short-lived allocat... -
- Rearranging the struct to have two 32-bit values next to each other
allows the struct to be one word smaller on 64-bit.
This lowers overall memory use as we have many methods out-of-the box:
$ /usr/bin/time ./ruby -e exit
0.06use... -
- As a point of comparison, I've often heard members of the Python community refer to the original implementation as "CPython". Also, not that this should necessarily carry any weight, but it's worth noting that CPython has its own page on...
-
- Neither "MRI" nor "CRuby" sounds official. They just emerged out of the community using it. I believe the official name of the implementation is Ruby. When you need to distinguish it from other implementations, I think you can use words ...
-
02:34 PM Misc #9438: Implementation naming
- I suppose all agree that
1. this only relates to documentation (not to the binary name), and that
2. as a general rule "Ruby" should be used whenever possible.
*But*: There are cases where a distinction between different imple... -
- Should we also change the name of the binary created when you make
to be MRI for instance to let users type `MRI -ropen-uri -e...` ?
It is almost self-evident that the implementation is explicitly
named `ruby`. -
01:20 PM Misc #9438: Implementation naming
- Yorick Peterse wrote:
> > Issue #9438 has been updated by Hiroshi SHIBATA.
> ...
This seems to be a non-issue for most other languages. Usually a language X
and its *first* implementation are used interchangeably, and I would rather s... -
12:49 PM Misc #9438: Implementation naming
- > Issue #9438 has been updated by Hiroshi SHIBATA.
> We should use "Ruby".
This would imply that MRI is the only Ruby implementation, or at least
the only one that matters. I'd say this is very far from the truth as
there are quit... -
- We should use "Ruby".
-
03:21 AM Misc #9438: Implementation naming
- A certain amount of streamlining is certainly a good thing, but we
should be aware that people use both "CRuby" and "MRI", often
indifferently. We should make sure that people who only understand one
of them, or who don't understa... -
- There seems to be an unclear decision on what to call this implementation.
We should make a decision between CRuby and MRI and update relating documentation to use one of them.
This discussion is based off a [ticket on ruby-lang.or... -
07:40 PM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Jeff Hodges wrote:
> On my local machine, that patch does give a Probably Okay response, having removed the TLS compression and the weak cipher suites. Thank you very much for your work and patience.
Thanks for taking an additional l... -
- On my local machine, that patch does give a Probably Okay response, having removed the TLS compression and the weak cipher suites. Thank you very much for your work and patience.
-
- Dirkjan Bussink, and Sam Kottler,
Thank you for commenting, but I'd like to drop my suggestion since emboss presented his direction. Could you please contribute by commenting/reviewing his patch?
Emboss, thank you as always with all... -
- First some words why I (and others here) believe that it's not a good idea to deviate from OpenSSL defaults:
Security is a delicate issue and typically consumers relying on a library like OpenSSL often do so because they don't want to... -
- Dirkjan Bussink wrote:
> Yusuke Endoh wrote:
> ...
I'm also completely willing to spend my time helping make ruby more secure. I really hope ruby-core will take Dirkjan, Jeff, and myself and any others who step up on our offers.
> ... -
- Yusuke Endoh wrote:
> Please give us not only words but also a concrete plan.
As said in the original mailing list, I'm more than willing to maintain this list for Ruby.
> ...
Actually OpenSSL already provides information on ... -
- Charlie Somerville wrote:
> Several members of the community have already offered to assist in maintaining more secure defaults in the OpenSSL extension.
Please give us not only words but also a concrete plan.
The following is j... -
- Charlie Somerville wrote:
> Shyouhei Urabe wrote:
> ...
Sorry, I said too much.
> Several members of the community have already offered to assist in maintaining more secure defaults in the OpenSSL extension.
> ...
I have been readi... -
- shyouhei@ruby-lang.org wrote:
>
> We are amateur about security. It might be possible to change
> something, then we have no idea what happens with that modification
> and even worse, we cannot maintain that bit when security rese... - 07:15 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Shyouhei Urabe wrote:
> Security is hard because NO ONE HELPS US BUT JUST COMPLAIN. Fuck off.
This is a completely unreasonable reply.
Several members of the community have already offered to assist in maintaining more secure defa... -
- Samuel Leslie wrote:
> Nobuyoshi Nakada wrote:
> ...
So do ruby. Don't know what OS you're using but the situation doesn't change between OpenSSL and Ruby in vast majority of Linux
distributions, maybe also on BSDs.
> Nobuyoshi Na... -
06:20 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Nobuyoshi Nakada wrote:
> Why won't they upgrade OpenSSL, but only Ruby?
OpenSSL on effectively all mainstream/general-purpose distributions tends to be a core system library which many applications depend on. This makes upgrading it... -
04:51 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- > Why won't they upgrade OpenSSL, but only Ruby?
I can't speak for everyone, but speaking for myself: before Jeff raised this issue I had no idea that OpenSSL was something I needed to pay attention to and consider upgrading. I vague... -
- Scott Gonyea wrote:
> Nobuyoshi Nakada wrote:
> ...
Why won't they upgrade OpenSSL, but only Ruby?
> OpenSSL 0.9.8 is the default on OS X and many still-supported Linux distros.
It's the responsibility of distributors.
Then we ... -
02:33 AM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- Nobuyoshi Nakada wrote:
> I agree the removal.
> ...
Those people are damned regardless. For anyone who does upgrade their version of Ruby, at the very least, this will protect them from OpenSSL's known / past insecure defaults. That ... -
- I agree the removal.
BTW, what's the reason you believe that people who don't upgrade even OpenSSL will upgrade Ruby? -
- * tool/ytab.sed: fix for Bison 2.6.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_2@44682 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
> No, sorry I see no evident speedup. When I wrote the patch I thought the
> function was used for Hash#rehash, but it turned out Hash#rehash uses
> something different (don't know why)... -
- On 01/21/2014 11:38 AM, Eric Wong wrote:
>> https://github.com/shyouhei/ruby/commit/f7ca891
>
> Thanks! However, I wasn't able to show a difference with
> "make benchmark"[1]. Were you?
>
> Perhaps rehash is not called often ... -
- Applied in changeset r44681.
----------
thread/thread.c: no dup
* ext/thread/thread.c (Init_thread): ConditionVariable and Queue
are not able to copy. [ruby-core:59961] [Bug #9440] -
05:32 AM Bug #9440 (Closed): Calling methods on a `Queue.new.dup` or `Queue.new.clone` causes Segfault
- On all platforms with ruby-2.1.0 calling a Queue#method on a duped or cloned Queue results in a Segfault:
queue = Queue.new.dup
queue.empty? # Segfault
The same issue occurs when calling other Queue#methods. -
- * ext/thread/thread.c (Init_thread): ConditionVariable and Queue
are not able to copy. [ruby-core:59961] [Bug #9440]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44681 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 06:22 AM Revision a658a5ae (git): * 2014-01-22
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44680 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44679 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Where is libgmp located in?
-
- miniruby will not load and gets an error of:
```
linking miniruby
Could not load program ./miniruby:
Dependent module libgmp.a(libgmp.so.10) could not be loaded.
Could not load module libgmp.a(libgmp.so.10).
System error:... -
01:58 AM Feature #9428: Inline argument expressions and re-assignment
- Indeed limiting it to method calls on the argument object (e.g `arg.to_i`) would make it much easier to parse and more readable, but greatly limits the potential application. It seems the inferencing in the initial proposal is the cause ...
-
01:12 AM Feature #9428: Inline argument expressions and re-assignment
- Tom Wardrop wrote:
> In some respects, you could consider it type hinting for a dynamic language. While statically typed languages would have a type hint., in dynamically typed languages, it's not uncommon for one to check and coerce ...
01/21/2014
-
- I'm mildy in favor of overriding OpenSSL defaults for now.
However I suggest removing openssl from the standard library to
encourage saner SSL implementations.
IMNSHO, OpenSSL is a disaster. -
09:50 PM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- There are many other places where Ruby takes a stance intended to avoid users shooting themselves in the foot. For example:
irb(main):008:0> rd, wr = IO.pipe
=> [#<IO:fd 7>, #<IO:fd 8>]
irb(main):009:0> rd.close_on_exec ... -
07:53 PM Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- +1
-
- Nobuyoshi Nakada wrote:
> This is primarily an issue of OpenSSL.
> ...
Waiting for OpenSSL to fix these things means that they will never get fixed. Even if somehow these defaults/options do disappear it will take years for people to b... -
- This is primarily an issue of OpenSSL.
And the next candidates are OS/Platform/Packager providers.
Fixing all other tools is the last resort. -
- I just wanted to remind everyone of the discussion that took place regarding adding RBTree to stdlib in [Feature #2348]
-
- Theres a discussion going on about possibly removing dependency on RBTree, or SortedSet all together.
Please see #9121 -
01:39 PM Revision 3ffc7535 (git): Several more OS information for TYPE_IP_MULTICAST_LOOP and
- TYPE_IP_MULTICAST_TTL.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44678 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:01 PM Misc #8741: email notification on bugs.ruby-lang.org is broken
- but I got notification about my last message, removed the flag `I don't want to be notified of changes that I make myself` from account settings and trying again :)
-
- I can confirm this still does not work - I did not get notification for last comment and neither closing the ticket.
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44677 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44676 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset r44675.
----------
thread_pthread.c: fix for dynamic PTHREAD_STACK_MIN
* thread_pthread.c (rb_thread_create_timer_thread): fix for platforms
where PTHREAD_STACK_MIN is a dynamic value and not a compile-time
con... -
08:53 AM Bug #9436 (Closed): r44670以降Solaris10でthread_pthread.cがコンパイルエラー
- r44670以降、Solaris10のccでは以下のエラーが出て失敗します。(以下はr44673にて確認)
cc -xO1 -xtarget=sparc64viiplus -m64 -DRUBY_EXPORT -I/usr/local/64/lib/libffi-3.0.10/include -I/usr/local/64/include -I. -I.ext/include/sparc64-solaris2.10 -I./include -I. -o th... -
- * thread_pthread.c (rb_thread_create_timer_thread): fix for platforms
where PTHREAD_STACK_MIN is a dynamic value and not a compile-time
constant. [ruby-dev:47911] [Bug #9436]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44675 ... -
- Thank you both for the feedback, I'm going to apply your suggestions and ping back when its ready.
-
- Thank you for clearing out what I want to say.
And split up internal/external sounds good idea.
(both document will be public) -
- Patch by @ykzts [Fix GH-484] https://github.com/ruby/ruby/pull/484
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44674 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44673 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Patch by @nruth on documenting-ruby/ruby#22
https://github.com/documenting-ruby/ruby/pull/22
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44672 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Applied in changeset r44671.
----------
thread_pthread.c: expand timer thread stack size
* thread_pthread.c (rb_thread_create_timer_thread): expand timer
thread stack size to get rid of segfault on FreeBSD/powerpc64.
based on the p... -
05:43 AM Bug #8783: ruby 1.9/2.0 crash on exit on FreeBSD/powerpc64
- There is a back trace of this issue here:
http://lists.freebsd.org/pipermail/freebsd-ruby/2014-January/003968.html
And I've attached a proposed patch. -
- * thread_pthread.c (rb_thread_create_timer_thread): expand timer
thread stack size to get rid of segfault on FreeBSD/powerpc64.
based on the patch by Steve Wills at [ruby-core:59923].
[ruby-core:56590] [Bug #8783]
git-svn-id: svn+... -
- * thread_pthread.c (rb_thread_create_timer_thread): define the stack
size for timer thread at compile time.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44670 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- You don't need quotes there.
-
05:29 AM Bug #9435 (Rejected): Kernel.system problem
- if ENV['PATH'] include double quotes, Kernel.system cann't find it.
windows OS, open a cmd window
```
set PATH="C:\Program Files\7-Zip";%PATH%
7z -h # can run it
pry
system '7z -h' # can't find
```
and, if command inc... -
04:57 AM Bug #9434 (Closed): Segfault on bundle exec rackup of a Sinatra app
- Hi,
I installed ruby using "ruby-install ruby 2.0" on an iMac of the following spec:
Processor: Intel Core i5 2.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 4 GB
Bo... -
- Takashi Oguma wrote:
> Should we introduce another symbol such as :xml_doctype_quote, or change the :xml_declatation_quote to :xml_prologue_quote or something?
Either way is fine by me, but maybe it's best to just use one symbol (:... -
- > I do not see why the person or machine that reads the first line of method's definition needs to know how the arguments will be post-processed before being further post-processed
Semantically, it just seems more appropriate to defin... -
- shyouhei@ruby-lang.org wrote:
> Plus I think you have more rooms for optimizations by sticking to
> power-of-two sized bins. When you rehash a hash, right now all
> elements are cleaned up from the bin, resize it, then insert them
...