Activity
From 12/27/2018 to 01/02/2019
01/02/2019
-
10:41 PM Feature #14344: refine at class level
- I'm also also using refinements a lot and in most cases I use "inlined" refinements, so would be glad to have a shorter syntax (and, actually, have been thinking about it for a long time and was going to propose a feature–and found this ...
-
10:37 PM Misc #15486: Default gems README.md
- As an example, I've created such a "default gem explanation" file as PR to the matrix library, see here: https://github.com/ruby/matrix/pull/7/files
What do you all think about this approach? -
- [The current documentation](http://ruby-doc.org/core-2.6/doc/syntax/refinements_rdoc.html) still states:
> When using indirect method access such as Kernel#send, Kernel#method or Kernel#respond_to? refinements are not honored for the ca... -
06:25 PM Bug #15400 (Closed): Ruby 2.6.0 broken string literal assignment to a local variable in Dir.tmpdir
- this has been fixed in webmock and released in 3.5.1
-
05:48 PM Bug #8140: Incorrect warning: `+' after local variable is interpreted as binary operator
- glyn (Glyn Normington) wrote:
> The statement:
> ...
The message as of ruby-1.9.3-p551 was:
~~~
$ ruby -w
'' +''
-:1: warning: `+' after local variable is interpreted as binary operator
-:1: warning: even though it seems like un... -
- This code appears to be working (not raising an exception) as early as Ruby 2.1.10:
~~~
$ ruby -v
ruby 2.1.10p492 (2016-04-01 revision 54464) [x86_64-darwin17.0]
$ irb
2.1.10 :001 > body, charset = "hey", "hey".encoding.to_s
=> ... -
- Shagabutdinov (Leonid Shagabutdinov) wrote:
> Shellwords.escape works incorrect under windows (tested for Windows 7
I don't believe `Shellwords` is intended to work on Windows at all. According to the comments (https://github.com/rub... -
02:10 PM Misc #15462: DevelopersMeeting20190110Japan
- * [Bug #15488] const_defined?("File::NULL") の挙動
* What is the expected behavior? -
12:27 PM Misc #15462: DevelopersMeeting20190110Japan
- * [Bug #15497] Encoding of error messages should not depend on the locale encoding (eregon)
* The behavior is unintuitive and makes it hard to test exception messages.
* [Bug #2250] IO::for_fd() objects' finalization dangerously clos... -
- Let me reopen this since the default is still dangerous and the original report is not solved.
-
- This seems to happen mostly for internal errors, as `raise` in Ruby code of course just uses the passed String's encoding for the message.
Example:
```ruby
name = "été"
p name.encoding
begin
Module.new.const_set(name, 1)
res... -
10:12 AM Feature #15496: Extract between string as standard String api
- Hmmm. I don't have a preference here since I can find arguments in favour or against
this. It's fairly easily possible to use a regex so .between (or any other name to
extract the substring between two boundaries) is not that necessar... -
08:51 AM Feature #15496 (Open): Extract between string as standard String api
- I could not find the a simple String api to extract the string between two string, and I notice that many face the same issue and endup rolling their own solutions (eg https://stackoverflow.com/questions/9661478/how-to-return-the-substri...
-
06:44 AM Bug #15495: Backport r66685, r66686 (Try to update cert)
- ruby_2_5 r66689 merged revision(s) 66685,66686.
-
- Backport 管理用チケットです。
r66685 と r66686 はテスト用証明書の期限切れに伴なう更新で安定版にも必要になります。 -
- Try to update cert
Try to update cert (2nd try)
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_5@66689 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:26 AM Bug #15494 (Closed): Fix Random.urandom in a chroot on OpenBSD
- r64625 broke `Random.urandom` because it uses `OpenBSD` as a macro when it is not defined. You must include the `sys/param.h` header to define the macro. I've tested the attached patch and it fixes `Random.urandom` usage inside a chroo...
-
04:25 AM Bug #15491 (Closed): r62701 introduced the incompatibility of Complex#+, #-, and #* removing #ifndef PRESERVE_SIGNEDZERO
- Applied in changeset trunk|r66688.
----------
complex.c: fix against redefining component methods
This fixes the incompatibility (maybe unintentionally) introduced by
removal of `#ifndef PRESERVE_SIGNEDZERO` guards in f_add, f_mul, and... - 04:25 AM Revision ee2ddf54 (git): complex.c: fix against redefining component methods
- This fixes the incompatibility (maybe unintentionally) introduced by
removal of `#ifndef PRESERVE_SIGNEDZERO` guards in f_add, f_mul, and
f_sub functions in r62701. [Bug #15491] [ruby-core:90843]
git-svn-id: svn+ssh://ci.ruby-lang.org/... - 04:18 AM Revision 888ddda1 (git): test/net/fixtures/Makefile: moved from test/net/imap
- This Makefile can be used to update test certificates. It should have been
moved at which the certificates was moved at r56836.
[ci skip]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66687 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:29 AM Revision 1e0b49a2 (git): Try to update cert (2nd try)
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66686 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66685 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 01:36 AM Revision 6d957b2f (git): complex.c: fix indentation
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66684 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:23 AM Bug #15493 (Closed): Seg Fault on 'vagrant up' Fedora29 intel
- This vm worked yesterday, but today it seg faulted when I ran 'vagrant up'
/usr/share/gems/gems/nokogiri-1.8.5/lib/nokogiri/xml/searchable.rb:198: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.5.3p105 (2018-10-18 revision 651...
01/01/2019
-
11:14 PM Feature #15492 (Open): Let #dig take a "default value" block like Hash#fetch does
- [fetch](https://ruby-doc.org/core-2.6/Hash.html#method-i-fetch) provides multiple ways to handle the case where a key can't be found:
> If the key can't be found, there are several options: With no other arguments, it will raise a Key... -
10:58 PM Feature #13618: [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
- normalperson (Eric Wong) wrote:
> > https://bugs.ruby-lang.org/issues/13618
> ...
Eric, FYI, something is wrong with native threads on osx in this update(though I'm not sure if it worked before)
code example:
```ruby
# test.rb
requ... - 10:49 PM Revision f43b38ab (git): * 2019-01-02
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66683 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:49 PM Revision 8b70a215 (git): suppress warning: method redefined; discarding old + introduced at r66681
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66682 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:13 PM Feature #15240: Set operations check for is_a?(Set), rather than allowing duck typing
- Thanks for chiming in, @knu!
Interestingly in <https://github.com/ruby/spec/pull/629> we had discussed and were considering that the existing `#to_set` could be seen as an *implicit* conversion, but as you've pointed out, the current ... -
- I made a patch https://github.com/ruby/ruby/pull/2062
-
- In r62701, preprocessor conditions `#ifndef PRESERVE_SIGNEDZERO` in `f_add`, `f_mul`, and `f_sub` functions were removed.
These changes introduced the incompatibility for some special cases.
For example, the results of the following ... - 12:20 PM Revision 5f908454 (git): complex.c: Optimize Complex#+ for some conditions
- Optimize f_add defined in complex.c for some specific conditions.
It makes Complex#+ about 1.4x faster than r66678.
Compared to r66678:
```
mrkn-mbp15-late2016:complex-optim-o3 mrkn$ make benchmark ITEM=complex_float_ COMPARE_RUBY=/Use... - 12:20 PM Revision 8d473272 (git): benchmark/complex_float_*.yml: New benchmarks
- Add new benchmark scripts for binary operations of Complex with float
components.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66680 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:09 AM Feature #15477: Proc#arity returns -1 for composed lambda Procs of known arguments
- Looks not a bug to me. Moving to the feature tracker.
A patch is attached.
```diff
diff --git a/proc.c b/proc.c
index c09e845ec0..45e2a21551 100644
--- a/proc.c
+++ b/proc.c
@@ -3063,6 +3063,16 @@ compose(VALUE dummy, VALUE a... -
09:52 AM Revision 11ba186c (git): test_jit.rb: test methodref insn
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66679 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
04:53 AM Revision 6e7213f4 (git): Merge rubygems-3.0.2.
- https://blog.rubygems.org/2019/01/01/3.0.2-released.html
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66678 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Applied in changeset trunk|r66676.
----------
compile.c (iseq_set_sequence): fix branch coverage table
Not only TRACE_ELEMENT but also INSN_ELEMENT may have events.
The old pc2branchindex was created using only events of TRACE_ELEMENTs... -
- Sorry, I wrote a wrong ticket number.
-
- Applied in changeset trunk|r66670.
----------
compile.c: support branch coverage for `a&.foo = 1`
[Bug #15476] - 03:03 AM Revision f77d3811 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66677 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Not only TRACE_ELEMENT but also INSN_ELEMENT may have events.
The old pc2branchindex was created using only events of TRACE_ELEMENTs.
This change uses events of INSN_ELEMENTs too for pc2branchindex table.
[Bug #15476]
git-svn-id: svn+s... -
- Applied in changeset trunk|r66674.
----------
compile.c: support branch coverage for `a&.foo = 1`
[Bug #15475] - 01:51 AM Revision 99d36318 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66675 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Bug #15475]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66674 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 01:47 AM Revision 7e035dcd (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66673 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66672 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 01:41 AM Revision 04dec2df (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66671 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Bug #15476]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66670 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
12/31/2018
-
07:30 PM Bug #15362: [PATCH] Avoid GCing dead stack after switching away from a fiber
- This still looks like it's waiting on a backport to Ruby 2.5. Also, does anyone know when the next release of the Ruby 2.5 branch will be done?
Thanks! -
- This can probably be closed as a dup of https://bugs.ruby-lang.org/issues/14561
-
- I believe this was fixed here: https://bugs.ruby-lang.org/issues/15362
-
03:00 PM Feature #12125 (Closed): Proposal: Shorthand operator for Object#method
- Applied in changeset trunk|r66667.
----------
Method reference operator
Introduce the new operator for method reference, `.:`.
[Feature #12125] [Feature #13581]
[EXPERIMENTAL] -
- Applied in changeset trunk|r66667.
----------
Method reference operator
Introduce the new operator for method reference, `.:`.
[Feature #12125] [Feature #13581]
[EXPERIMENTAL] - 03:00 PM Revision 8423533c (git): * 2019-01-01
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66669 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 03:00 PM Revision d935a0ab (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66668 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Introduce the new operator for method reference, `.:`.
[Feature #12125] [Feature #13581]
[EXPERIMENTAL]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66667 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 02:59 PM Revision 4a6f7633 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66666 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66665 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66664 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I'd like to help out, too.
Maybe we can have a second file `README-DEFAULT-GEM.md` which is linked to by the `README.md`. The `README-DEFAULT-GEM` would explain how default gems work etc. and would be same for all default gems and wou... -
- that randomly fails
https://rubyci.org/logs/mswinci.japaneast.cloudapp.azure.com/vc12-x64/ruby-trunk/log/20181231T103312Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66663 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:28 AM Feature #10548: remove callcc (Callcc is now going obsoleted. Please use Fiber.)
- FWIW, I do have a practical example for `callcc` which cannot be implemented with fibers, or at least I don't see the way it could.
I'm the author of the [dry-monads](https://github.com/dry-rb/dry-monads/) gem. Along with a bunch of mon... -
- Always it happens here, though I couldn't find the source of `si_destination_compare`, it may be a problem in libsystem_info.dylib.
```
7 ??? 0x00007fc6cddeaac0 0 + 140491834174144
8 libsystem_trace.dy... -
03:46 AM Bug #15490 (Third Party's Issue): socket.rb - recurring segmentation faults
- With Ruby 2.5.3p105 and now with Ruby 2.6.0 following our recent upgrade, we are sadly still seeing reasonably frequent segmentation faults from Ruby, specifically within socket.rb
Looking in socket.rb, it seems it's related to the ad... -
- ko1 (Koichi Sasada) wrote:
> naruse (Yui NARUSE) wrote:
> ...
Sure, thank you for comment.
ioquatix (Samuel Williams) wrote:
> Thanks I didn’t know approval procedure.
> ...
Anyway please update NEWS now to avoid forgetting adding... -
03:48 AM Feature #15485 (Rejected): Refactor String#split
- 01:14 AM Revision d7c7382f (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66662 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * load.c (rb_resolve_feature_path): search the path for already
loaded feature.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66661 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:09 AM Revision c5e8627f (git): Revert "lib/net/http.rb: use connect_timeout instead of Timeout"
- This reverts commit 69a1db96fe63ff3071cb3d272675a1d0470aab01.
getaddrinfo(3) doesn't support timeout.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66660 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- lib/net/pop.rb: ditto
lib/net/ftp.rb: ditto
lib/net/smtp.rb: ditto
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66659 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
12/30/2018
-
09:56 PM Feature #10344: [PATCH] Implement Fiber#raise
- Thanks I didn’t know approval procedure.
I will update NEWS one I’m sure the feature has stabilised. -
05:44 PM Feature #10344: [PATCH] Implement Fiber#raise
- naruse (Yui NARUSE) wrote:
> @ioquatix Is this feature accepted by matz?
> ...
this is a support comment.
Matz agreed this feature several years ago (maybe I'm only person against, and I also agree to introduce this feature now, exc... -
- @ioquatix Is this feature accepted by matz?
A change which is visible from Ruby and non trivial bugs requires matz's approval.
And also you need to add description to NEWS if you add new feature. -
- Applied in changeset trunk|r66658.
----------
vm_args.c: search symbol proc in super classes
* vm_args.c (refine_sym_proc_call): traverse ancestors to search
inherited methods for symbol proc.
[ruby-dev:50741] [Bug #15489] -
11:05 AM Bug #15489 (Closed): SEGV when using refinements and `&:` syntax
- # Sample code
~~~ ruby
# segv.rb
module ArrayExt
refine Array do
end
end
class MyHash
def initialize(hash = {})
@hash = hash
end
def method_missing(key)
if @hash.key?(key)
@hash[key]
else
... -
- * vm_args.c (refine_sym_proc_call): traverse ancestors to search
inherited methods for symbol proc.
[ruby-dev:50741] [Bug #15489]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66658 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:42 PM Misc #15487: Clarify default gems maintanance policy
- @naruse Sorry if my original request was sounding too aggressive, just stating "something is wrong" is never my intention.
> Such historical reasons are hard to explain.
Yes, I understand that.
> ...
I understand that too. That... -
- Some of libraries has upstream and others are originated in ruby repo.
And some upstreams are not maintained but some of such libraries are transfered its privilege to hsbt.
Such historical reasons are hard to explain.
OSS project d... -
- OK, after a bit of thinking, this makes perfect sense to me.
Please close, and sorry for misreporting. -
- As @mame said, that's what `to_enum` is for.
There is no way we are going to modify all forms not returning Enumerators, when there's already a good solution (that's shorter than the proposition!).
This request should be closed. -
- > Personally I like this style because it is very clear and explicit. Anyway.
Well, on its own as just 2 code lines it probably is.
But any realistic use-case I can see of is like, for example "take all lines before empty line (extra... -
- zverok (Victor Shepelev) wrote:
> ```ruby
> ...
(Personally I like this style because it is very clear and explicit. Anyway.)
There is `Object#to_enum` for your use case.
lines.to_enum(:split, "\n").select {|ln| ln.match?(PA... -
- * It declares clocks which are invalid for clock_gettime(), which I consider OS bug.
* I want to keep testing all declared clocks on other platforms.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66657 b2dd03c8-39d4-4d8f-98ff-823fe6... - 05:47 PM Revision 8b8e5246 (git): * 2018-12-31
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66656 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * This reverts commit a7edd05f7dca44f56fd72d7bcc232e1b27df0eb3.
* I prefer to exclude Solaris, I want to keep testing these clocks on Linux/macOS.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66655 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66654 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset trunk|r66653.
----------
vm.c: Move the rdoc of RubyVM.resolve_feature_path [Bug #15482] -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66653 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:26 AM Misc #15486: Default gems README.md
- I just come across this issue. I wanted to point out that I've been working on the:
* https://github.com/ruby/logger
* https://github.com/ruby/fileutils
* https://github.com/ruby/irb
* https://github.com/ruby/rake
Repositories f... -
- 挙動を修正したパッチを書いてみました。
ただ、意図的にそのような実装にしていた節があるのでこれが仕様なのかバグなのかは現時点で判断するのはちょっとむずかしそうですね。
該当箇所を消してもテストはパスしていたんですが…。
わたしも処理に一貫性を持たせるためには `true` を返したほうがいいと思います。
* pull requst : https://github.com/ruby/ruby/pull/2061
また、元々は以下の issues で議論... -
06:09 AM Bug #15488: const_defined?("File::NULL") の挙動
- なるほどー。そういう違いがあるんですね。
そうすると、`File.const_defined?("NULL")` は `true` になることと、
`Object.const_get("File::NULL")` との一貫性の観点から
`Object.const_defined?("File::NULL")` も `true` になるほうが良いような気がします。 -
- ちょっと調べてみたんですが、次のように `include` したモジュールの定数の場合は `false` が返ってくるのが原因なようですね。
```ruby
module M
HOGE = 42
end
class X
include M
end
p Object.const_get("X::HOGE") # => 42
p Object.const_defined?("X::HOGE") # => false
... -
- `File.const_defined?` だと `true` になるようですね。
```ruby
p Object.const_get("File::NULL") #=> "/dev/null"
p Object.const_defined?("File::NULL") #=> false
p File.const_get("NULL") #=> "/dev/null"
p File.const_defined?("NULL... -
- `const_get` と `const_defined?` について、例えば `Math::PI` では以下のようになり
どちらも期待通りの結果になります。
~~~ruby
p Object.const_get("Math::PI") #=> 3.141592653589793
p Object.const_defined?("Math::PI") #=> true
~~~
一方、`File::NULL` の場合は以下のように... -
- fixes r66593 in a better way like r66646.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66652 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- https://rubyci.org/logs/mswinci.japaneast.cloudapp.azure.com/vc12-x64/ruby-trunk/log/20181230T041101Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66651 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10x/ruby-trunk/log/20181230T041806Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-trunk/log/20181230T042407Z.fail.html.gz
https://rubyci.org/logs/rub... -
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/opensuseleap/ruby-trunk/log/20181230T040002Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66649 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:15 AM Revision 6b861342 (git): Unset SOURCE_DATE_EPOCH on Rubygems test cases
- Relates to r66554. When test suites run with SOURCE_DATE_EPOCH, several
tests would fail. Environment Variables are already kept with this
setup & teardown phase.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66648 b2dd03c8-39d4-4d... -
- * [Feature #15373] Proposal: Enable refinements to `#method` and `#instance_method`
* [Feature #15374] Proposal: Enable refinements to `#method_missing`
* [Bug #15416] 配列リテラル内の引数を伴う括弧なしのメソッド呼び出しで syntax error
-
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/amazon/ruby-trunk/log/20181229T153003Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66647 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 12:46 AM Revision 230fe418 (git): accept_nonblock_spec: IO.select instead of sleep
- Waiting on socket I/O using IO.select should work on all platforms.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66646 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66645 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
12/29/2018
-
- Applied in changeset trunk|r66644.
----------
Update NoMethodError/NameError docs [ci skip]
[ruby-core:90796] [Bug #15481]
From: zverok (Victor Shepelev) <zverok.offline@gmail.com> -
- * Add missing `receiver:` to `NoMethodError.new`;
* Document `receiver` and `private` argument of `NoMethodError.new`;
* Add explanations/examples about receiver to `NameError.new`;
* Reformat both methods call-sequences in a modern w... -
- [ruby-core:90796] [Bug #15481]
From: zverok (Victor Shepelev) <zverok.offline@gmail.com>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66644 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
-
- RDoc requires method docs to be in the same `.c` file as `rb_define_method`, so despite method docs were present in source, they were ignored: https://ruby-doc.org/core-2.6/RubyVM.html
The patch fixes it. -
-
- Thanks. No problem.
-
- Improvements:
* Mention new `:script_compiled` event;
* Deduplicate `__enable`/`enable` methods;
* Document `target:` and `target_line:` arguments.
I am not sure that `target` explanations and examples are sufficient and unambiguo... -
-
- I've stared improving the README for the [matrix gem](https://github.com/ruby/matrix).
Feel free to provide PRs for it, and it could serve as a model for the others. -
- While working on [Ruby Changelog](https://bugs.ruby-lang.org/issues/15485), I noticed the following.
A lot of parts of stdlib is extracted currently into "default gems". This, in my understanding, means (amongst other things) their de... -
- `json` is not a good example of default gems. Because I and nalsh got the only commit bit of `flori/json` at recently, not release a grant of rubygems.org.
-
- Much of this is in this [list of maintainers](https://github.com/ruby/ruby/blob/trunk/doc/maintainers.rdoc) and [basic maintainers guidelines](https://bugs.ruby-lang.org/projects/ruby/wiki/MaintainerDischargingProcess)
As for the `jso... -
- In addition to #15486, I'd like to raise the question of the general _maintanance policy_ for "default" Ruby gems, in particular:
* who is responsible for each gem and how they should be contacted?
* what are goals and policies for gem... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66643 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66642 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-ad7f67/ruby-trunk/log/20181229T135406Z.fail.html.gz
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/rhel_zlinux/ruby-trunk/log/20181229T143303Z.fail.html.gz
git-svn-id: svn+ssh://c... -
09:03 PM Bug #15478: [RFC] erb: remove deprecation warnings from ERB.new
- takashikkbn@gmail.com wrote:
> Status changed from Third Party's Issue to Assigned
Thanks for fixing.
> > Why change existing behavior at all?
> That's because leaving a legacy code might confuse those who
> read the code an... -
- for $SAFE deprecation, I partially applied your change in r66632 as well, in addition to reverting my change for Ruby 2.7.
-
- Applied in changeset trunk|r66631.
----------
Revert "erb.rb: print deprecation warning with warn level 1"
This reverts commit b5569b9ab2ad5e0e4a997df7eb73e97ecbacc9dd.
The deprecation is indefinitely postponed.
[Bug #15478] -
- > Why change existing behavior at all?
That's because leaving a legacy code might confuse those who read the code and decreases the maintainability. I like to keep implementation simple so that we don't lose the speed of implementing... -
- takashikkbn@gmail.com wrote:
> Issue #15478 has been updated by k0kubun (Takashi Kokubun).
>
>
> > nil and 0 $SAFE is already no-op, already, right? I don't care about $SAFE, so I would expect people will pass nil or 0 when they ... -
- I don't know how to send a patch to your git repository, so I attached it in this ticket.
I will still welcome your opinion on this thread, but at least I'm going to eliminate the second argument once $SAFE is removed from Ruby itsel... -
- > nil and 0 $SAFE is already no-op, already, right? I don't care about $SAFE, so I would expect people will pass nil or 0 when they don't care (because they need to pass the other legacy variables).
> ...
I think you misunderstand that... -
- takashikkbn@gmail.com wrote:
> Stop showing warnings for legacy_trim_mode and legacy_eoutvar is fine.
OK.
> But why should we stop deprecating nil and 0 for
> safe_level? If we do so, this would be suddenly broken in Ruby
> 2.8... -
- > There's too much code relying on the old ordering
Also please provide real-world use cases for this. I saw many projects are rewritten to Ruby 2.6 interface before even Ruby 2.6 is officially released. We should fix such projects in... -
- Stop showing warnings for legacy_trim_mode and legacy_eoutvar is fine. But why should we stop deprecating nil and 0 for safe_level? If we do so, this would be suddenly broken in Ruby 2.8 or Ruby 3.0. So this change does not make sense fo...
-
- Thank you for the answers. I've started improving the README for the matrix gem according to this info.
-
- Applied in changeset trunk|r66640.
----------
`TracePoint#enable(target_thraed:)` [Feature #15473]
* vm_trace.c (tracepoint_enable_m): `TracePoint#enable` supports
`target_thread:` keyword to filter a target thread.
[Feature #15473] -
- * vm_trace.c (tracepoint_enable_m): `TracePoint#enable` supports
`target_thread:` keyword to filter a target thread.
[Feature #15473]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66640 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 04:29 PM Revision fd7d4a87 (git): * 2018-12-30
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66639 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * internal.h: move ar_table def to hash.c because other files
don't need to know implementation of ar_table.
* hash.c (rb_hash_ar_table_size): added because gc.c needs to know
the size_of(ar_table).
git-svn-id: svn+ssh://ci.ruby-l... -
02:50 PM Bug #14714: Ruby 2.5.1 Segmentation Fault in GC
- I just ran my test suite 5 times with Ruby 2.6.0 on macOS 10.14.2 and have not been able to reproduce this crash anymore.
Could you please all check if you still see this crash with the latest release? -
- Old tickets with no reaction/vague reaction:
* [Feature #14444] `MatchData`: alias for `#[]`
* [Feature #14784] `Comparable#clamp` with a range
* [Feature #14145] Better `Method#inspect`
New tickets:
* [Bug #15428] Refactor `Proc#... -
10:41 AM Misc #15462: DevelopersMeeting20190110Japan
- * [Feature #15483] Proc or Method combination with Symbol
-
- I think it is not good to assume that it is unidiomatic per se, at the least not the code that was
shown, e. g.:
lines.split("\n") { |ln| result << ln if ln.match?(PATTERN) }
I myself would possibly not write code like this, b... -
- In #4780, new "block form" of `#split` was introduced. It behaves this way:
```ruby
"several\nlong\nlines".split("\n") { |part| puts part if part.start_with?('l') }
# prints:
# long
# lines
# => "several\nlong\nlines"
```
... -
- I am biased so I do not want to digress from this thread too much while explaining my bias. However had,
I still want to state a few things:
- In regards to Symbol, this is a language design decision, how Symbols are to be used. I th... -
- In [Feature #6284], Matz said
> We need more discussion if we would add combination methods to the Symbol class.
Right, let's get started to discuss.
For your information, recent a few months I'm discussing this with @osyo .
... -
- Thanks!
-
- Applied in changeset trunk|r66637.
----------
process.c: document system(..., exception: true) [ci skip]
From: Victor Shepelev <zverok.offline@gmail.com>
[Bug #15480] -
- While working on [Ruby Changelog](https://rubyreferences.github.io/rubychanges/), I noticed some of new functionality of 2.6 is not documented.
I'll create several tickets to address problems discovered.
Current one is about `Kerne... -
- From: Victor Shepelev <zverok.offline@gmail.com>
[Bug #15480]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66637 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66636 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66635 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- on mswin RubyCI by Permission Denied.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66634 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- `Errno::EINVAL: Invalid argument - clock_gettime` could occur even on Linux.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66633 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- oops, closed this ticket by a wrong ticket number in my commit... reopening.
-
- Applied in changeset trunk|r66632.
----------
erb.rb: increase warn level only when non-zero safe_level
is given.
This is merging Eric's patch in [Bug #15479] to Ruby 2.6's behavior in r66631. -
-
- Oops, I copy-pasted the ticket number in the commit message, but actually it should have been Feature #15349.
-
- This is a smaller reproducible code.
```
mrkn-mbp15-late2016:bigdecimal mrkn$ cat t.rb
def foo
a = [1, 2, 3, 4]
a.reject! {|x|
next true if x == 2
return a if x == 3
false
}
end
p foo
p foo
mrkn-mbp15-l... -
- @tenderlovemaking According to git bisect, https://github.com/ruby/ruby/commit/d46cd60f3cfb88f1591d6ce0f23e750d3833434f (Feature #15289) seems to have triggered this. Could you check it?
-
- is given.
This is merging Eric's patch in [Bug #15479] to Ruby 2.6's behavior in r66631.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66632 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- This reverts commit b5569b9ab2ad5e0e4a997df7eb73e97ecbacc9dd.
The deprecation is indefinitely postponed.
[Bug #15478]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66631 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/amazon/ruby-trunk/log/20181229T033003Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66630 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to avoid random failures like
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11s/ruby-trunk/log/20181229T032506Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66629 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to prevent random failures like
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian8/ruby-trunk/log/20181229T033003Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66628 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- this exists for `context "when passed close_others: false" do`, but this
seems to be missing for `context "when passed close_others: true"`.
And this seems to hang forever on Windows since r66622.
https://ci.appveyor.com/project/ruby/rub... -
- Even 60s is short for our CI environments:
https://rubyci.org/logs/rubyci.s3.amazonaws.com/amazon/ruby-trunk/log/20181228T153002Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66626 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 01:51 AM Revision bfd1980d (git): * properties.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66625 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- introduced in r66622, but this does not succeed on Solaris
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-trunk/log/20181229T002409Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66624 b2dd03c8-39d4-4... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66623 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66622 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66621 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
12/28/2018
-
11:30 PM Bug #15479: Array#reject! modifies literal Array
- Is the distinction really whether 2.6.0 & trunk only modify the array if `reject!` successfully enumerates all array members?
But if so, why does it modify the first loop? Strange behavior...
-
- This was found by running ruby/spec with -R2 (such as mspec -R2 -fs core/array/reject_spec.rb).
TravisCI log on https://travis-ci.org/ruby/spec/jobs/473175799#L539
Here is a simple reproducer.
MRI seems to modify the Array literal p... -
- erb: remove deprecation warnings from ERB.new
There's too much code relying on the old ordering; so any
deprecation or removal of the old way is too annoying
and only serves to make users angry.
-
- @nobu cherry-picked the IO.copy_stream patch in r66147, and I now upstreamed it to ruby/mspec.
I mostly forgot about it, and it's easy enough for early Ruby implementations to shim IO.copy_stream. -
06:23 PM Feature #15166: 2.5 times faster implementation than current gcd implmentation
- your micro-benchmarks aren't always fair, because some algorithms don't handle all edge cases, different data types etc.
for jruby I choose a different algorithm that is slightly slower than the fastest gcdwikipedia7fast32 (~15%) but ... -
- As a note, it seems semantically `a << b` is the same as `a.replace(a + b)`.
I think this is good to keep, and therefore the discussion also applies to the resulting encoding of String#+. -
- duerst (Martin Dürst) wrote:
> In any way, when adding stuff to a (BINARY) buffer, the right thing conceptually is to change all the pieces to BINARY, not to rely on some of the pieces (be it the first or another) to be BINARY.
If th... -
- hi, such fallback already exists
https://github.com/ruby/ruby/commit/4cf460a7bb258d3d61414d2f74df4c0f83c6a3af
I don't know if your implementation is faster, but it's certanly not worth to optimize for platforms without `__builtin_ctz... - 03:19 PM Revision 2ceebcc3 (git): * 2018-12-29
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66620 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- we reached 30min timeout on osx build
https://travis-ci.org/ruby/ruby/jobs/473019623
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66619 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to stabilize AIX powerpc CI
https://rubyci.org/logs/rubyci.s3.amazonaws.com/aix71_ppc/ruby-trunk/log/20181227T113302Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66618 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- for now. This should be fixed, but let me make this new CI green
first to introduce Solaris-related changes later.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66617 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to stabilize CI failure like:
https://rubyci.org/logs/rubyci.s3.amazonaws.com/osx1013/ruby-trunk/log/20181228T114501Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66616 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- CC is changed from "icc" to "icc -std=c99" by r66605.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/icc-x64/ruby-trunk/log/20181228T130003Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66615 b2dd03c8-39d4-4d8f-98ff-... -
- to prevent random failures.
test/ruby/test_autoload.rb: ditto
test/ruby/test_optimization.rb: ditto
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-trunk/log/20181228T101706Z.fail.html.gz
https://rubyci.org/logs/mswinci... -
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/arch/ruby-trunk/log/20181228T090001Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66613 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- @nome can you review the relevant commits and give me feedback?
-
01:03 PM Feature #10344 (Closed): [PATCH] Implement Fiber#raise - Applied in changeset trunk|r66610.
----------
Implement Fiber#raise. Fixes #10344.
This allows raising exceptions in another fiber, similarly to
Thread#raise. - 01:03 PM Revision 78e3cd2b (git): Fix #endif annotation.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66612 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 01:03 PM Revision 9ee79b65 (git): Don't allow rb_fiber_resume to raise exception on unborn fiber.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66611 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 01:03 PM Revision 5fb9d1e1 (git): Implement Fiber#raise. Fixes #10344.
- This allows raising exceptions in another fiber, similarly to
Thread#raise.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66610 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 10:33 AM Revision b0d24baf (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66609 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66608 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66607 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This failure is a known issue that exists mainly on CI environments.
We should address this at some moment, but making CI red by this would
be just a false-positive alarm for now.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66606 ... -
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian8/ruby-trunk/log/20181228T063002Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-trunk/log/20181228T081706Z.fail.html.gz
https://rubyci.org/logs/rubyci.s... -
08:32 AM Bug #15460: Behaviour of String#setbyte changed
- Eregon (Benoit Daloze) wrote:
> Why are values higher in HexaPDF? Does it mean multiple bytes need to be written or is it enough to throw away the high bits?
> ...
This actually happens in the predictor filter of HexaPDF (see https://g... -
- Thank you for your comments.
> For sake of completion, I would recommend showing how/if we can target other threads too, and how it would look like.
I don't have good example, but there is a `Thread#set_trace_func` to specify the t... -
- * [Feature #6012] Proc#source_location also return the column
* Now we can implement the issue. -
- Now the abstract syntax tree has column information, so we can implement this issue. We even add the last point of method.
```
# test.rb
◆def foo # ◆: line 2, column 0
end★ # ★: line 3, column 3
p method(:foo).source_locati... -
05:31 AM Feature #12282: Hash#dig! for repeated applications of Hash#fetch
- Another naming idea is `#fetch_all`, signalling that this is essentially a `#fetch` over a list of keys.
-
- Thanks everyone, for the discussion. I realize that my original comparison with #dig had a typographical error. Here's a gem implementation, with examples that are correct: https://github.com/dogweather/digbang
```
require 'dig_bang'... -
- ```
f = -> x { x + 2 }
g = -> x { x * 2 }
h = f << g
f.arity # => 1
g.arity # => 1
h.arity # => -1 THIS SHOULD BE 1 because h "knows" that it takes exactly 1 argument:
h.call # => ArgumentError (given 0, expected 1)
```
La... -
04:52 AM Bug #15476: Branch coverage: Failing to load trivial sample when branch coverage is on
- Sorry, forgot to include the error message:
~~~
/tmp/ruby20181227-3429-1ubxjqu.rb:1:in `<top (required)>': no implicit conversion of false into Integer (TypeError)
~~~
-
- The following will fail (for the second #load) on 2.6.0
I assume this is Ruby removing useless code, and the branch coverage code handling it incorrectly.
~~~ ruby
require 'tempfile'
f = Tempfile.new(['ruby', '.rb'])
f.write(<<-RU... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66604 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66603 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- In the following code, only the first conditional call will appear in the result hash of the branch coverage. The second one will not because it is a setter. This appears to be a forgotten case for branch coverage.
~~~ ruby
require '... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66602 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:42 AM Revision 91dfdf84 (git): vm_insnhelper.c: USE_FLONUM is always defined
- This changeset should fix the 32bit failures.
See also: https://travis-ci.org/ruby/ruby/jobs/472855470
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66601 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:31 AM Bug #15469: Ruby2.6 included `bundler` does not handle specified `csv` gem.
- I need that CSV::VERSION indicates 2.4.8 as well as Workaround.
-
- What's the version of csv library that is you expected?
I wonder csv-1.0.0 on your Gemfile. -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66600 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- RUBYOPT is answered by shevegen. Thanks. It was also explained in release notes. And you can use "ruby --jit bin/rails s" as well. Why do we want to have more ways to specify that?
> which should only be respected by ruby >= 2.6.0
... -
- * Define major and minor version numbers only in the public
include/ruby/version.h header, as the API version numbers.
* Define only teeny version number in the private version.h
header.
* RUBY_VERSION moved to version.c.
git-svn-... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66598 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- - FIXNUM_2_P: moved to vm_insnhelper.c because that is the only
place this macro is used.
- FLONUM_2_P: ditto.
- FLOAT_HEAP_P: not used anywhere.
- FLOAT_INSTANCE_P: ditto.
- GET_TOS: ditto.
- USE_IC_FOR_SPECIALIZED_METHOD: ditto.... -
- So, we can close this ticket, right? Let me know if you still have any trouble.
-
- I agree we should fix this issue. It is very much unexpected behaviour and even context sensitive behaviour. Double splat operator should be required in all cases to turn hash into keyword arguments.
12/27/2018
-
- ko1 (Koichi Sasada) wrote:
> Maybe `Thread.current` is frequent pattern, so accepting :current` symbol is reasonable for me.
I think it's not needed, and that passing `Thread.current` is clearer and simpler, so I would propose to not... -
- To me personally the proposal seems fine. I like the shortcut :current for Thread.current
which makes sense (to me), as Thread.current already exists as name, so it appears intuitive
to me.
For sake of completion, I would recommend ... -
- We introduced `TracePoint#enable(target:, target_line:)` keyword.
How about to introduce `target_thread:` keyword which specify enabling threads?
```ruby
TracePoint.new(:line){|tp| p tp}.enable(target_thread: Thread.current) do
p... -
- There is some documentation at:
https://bugs.ruby-lang.org/projects/ruby/wiki/MJIT#Basic-usage
I believe Takashi and others may update that page every now and then.
To the suggestion of a new environment variable:
I have no p... -
09:58 PM Misc #15474 (Rejected): Running Rails with jit
- I have installed ruby-2.6.0
I want to try to run my rails app with the jit.
How can this be done?
I should try env RUBY_OPTS='--jit'
Is this the way the go?
The jit ist experimental, but promising,
so we need to try it wherever... -
- I wonder, what purpose do you envision for `instruction_sequence`?
It is of course MRI-specific (as documented), so I'm not sure how one would use it on other Ruby implementations.
> I named `eval_script` because we can not get sourc... -
- Nice - I did not know about MAINLIBS in RbConfig::CONFIG before either.
-
06:31 PM Bug #15470: Getting Jemalloc to work with 2.6.0
- mseneadza (Michael Seneadza) wrote:
> I ran into this the other day. Try:
> ...
Oh that did work for me too!
~~~
irb(main):001:0> puts RbConfig::CONFIG['MAINLIBS']
-lz -lpthread -lrt -lrt -ljemalloc -ldl -lcrypt -lm
~~~
-
05:53 PM Bug #15470: Getting Jemalloc to work with 2.6.0
- I ran into this the other day. Try:
~~~
irb(main):002:0> puts RbConfig::CONFIG['MAINLIBS']
-lpthread -ljemalloc -ldl -lobjc
~~~ -
- I have a install script that installs all build requirements for Ruby together with libjemalloc, it then configures Ruby with the --with-jemalloc flag, they were all run on Debian 9 which installs jemalloc 3.6.0 from the Debian repositor...
-
- > https://bugs.ruby-lang.org/issues/15472
Looks like [Bug #15468] and r66582 fixes it -
- It seems that invalid (JSON) data is being sent once the request's body passes a size threshold. I'm sending emails via the sparkpost.com API using the sparkpost_rails gem ( https://github.com/the-refinery/sparkpost_rails ). That gem us...
-
- Applied in changeset trunk|r66595.
----------
fix missed script_compiled events. [Bug #15471]
* ruby.c (process_options): script_compiled events are missed on
command line -e or specified file. this commit fix it.
[Bug #15471]
T... -
- Of course, `ruby -e ...` or `ruby script.rb` compile given ruby script. But `script_compiled` event is not kicked.
```
$ ruby -r sample x.rb
```
We can put TracePoint in sample library but we can't get `script_compiled` event on ... - 05:39 PM Revision d3c0b209 (git): * remove trailing spaces.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66596 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * ruby.c (process_options): script_compiled events are missed on
command line -e or specified file. this commit fix it.
[Bug #15471]
This patch should be backport to Ruby 2.6 branch.
* vm_core.h (rb_exec_event_hook_script_compile... -
- with NoMemoryError on TestMethod#test_splat_long_array.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/opensuseleap/ruby-trunk/log/20181227T080002Z.log.html.gz
Maybe better to check /proc/meminfo instead of /etc/os-release.
git-svn-i... -
- on solaris until it gets stable.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-trunk/log/20181227T142405Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66593 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 04:24 PM Revision 3e3b8df5 (git): * 2018-12-28
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66592 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- on AIX ppc
https://rubyci.org/logs/rubyci.s3.amazonaws.com/aix71_ppc/ruby-trunk/log/20181226T113305Z.fail.html.gz
test/lib/test/unit/assertions.rb: ditto, for TestIO#test_copy_stream_no_busy_wait
git-svn-id: svn+ssh://ci.ruby-lang.org/... -
- * [Misc #15347] Require C99
* Is it okay to require C99 features which work on both VC12 (Visual Studio 2013) and Oracle Developer Studio 12 from Ruby 2.7? https://github.com/ruby/ruby/pull/2064
* Note: 2 major concerns (mswin, sol... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66590 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset trunk|r66589.
----------
common.mk: pass CFLAGS to transform_mjit_header.rb
so that flags like -msse4.1 are passed when checking compilation status
in transform_mjit_header.rb. It matters for checking __builtin_xxx... -
- @k0kubun
the problem is that c compiler doesn't allow to use __builtin_xxx macros if not specifically enabled with arguments like -msse4.1, but transform_mjit_header.rb ignores all passed cflags for some reason.
this simple patch fix... -
- so that flags like -msse4.1 are passed when checking compilation status
in transform_mjit_header.rb. It matters for checking __builtin_xxx things.
[Fix GH-2059] [Bug #14964]
From: pavel <pavel.rosicky@easy.cz>
git-svn-id: svn+ssh://ci... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66588 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66587 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I want to use `csv` library which is same version of Ruby 2.5.
Because Ruby 2.6's csv library has some breaking changes and they break our product.
However, Ruby 2.6's `bundler` does not handle `csv` which I specified the version.
... -
12:42 PM Revision b7c2ca7a (git): [DOC] SecureRandom is extended by Random::Formatter.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66586 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66585 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- These settings are now covered by .dir-locals.el.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66584 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Recent Emacs (23 and up?) has this feature called .dir-locals.el.
See also: https://www.gnu.org/software/emacs/manual/html_node/emacs/Directory-Variables.html
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66583 b2dd03c8-39d4-4d8f... -
- ささだです。
日本語でも書いておきます。
RubyKaigi 2019
の前後の日に開発者会議ができればと思っています。前日は午後から、後日はまだ調整中です（まつもとさんは後日はいらっしゃらないと思います）。
・エントリー方法などは、チケットをご覧下さい。
・議論したいトピックなど、お寄せ下さい。
・招待したい方も、ご推薦下さい。
・福岡は宿の手配が大変らしいので、事前の手配をお忘れ無く。
どうぞよろしくお願いします。
-
- This commit should fix Net::Protocol::BufferedIO#write when sending
large multi-byte string like following example.
```
$ ruby -rnet/http -rjson -v -e "Net::HTTP.post(URI('http://httpbin.org/post'), { text: 'あ'*100_000 }.to_json, 'Conte... -
04:45 AM Bug #15468 (Closed): Net::Protocol::BufferedIO#write raises NoMethodError when sending large multi-byte string
- ruby-2.6.0で大きなJSON文字列をNet::HTTPでPOSTすると以下のように NoMothodError が発生するようになりました。
~~~
$ ruby -rnet/http -rjson -v -e "Net::HTTP.post(URI('http://httpbin.org/post'), { text: 'あ'*100_000 }.to_json, 'Content-Type' => 'application/json')"
ruby 2... - 04:21 AM Revision 1f866ddc (git): * 2018-12-27
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66581 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66580 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- We will fix this issue at https://github.com/rubygems/rubygems/pull/2549
-
- > But dropping old rubies will happen every year and it can affect gems to remove legacy code. If it is considered as breaking changes as you said, it will cause major bump and it's false positive for normal users who runs application wi...
-
- > Just for a point of reference, I use "~> x.y" for all my dependencies, as, taking into consideration semantic versioning, this allows for the maximum range of support but excluding breaking changes (i.e. x must stay the same, but y can...