Activity
From 04/08/2019 to 04/14/2019
04/14/2019
-
09:11 PM Bug #15766: Crash in 2.4, 2.5 involving at_exit
- Using a recent build (`ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]`), the code ran fine, or just like 2.6. I haven't checked on 2.4.
Using the current RubyInstaller release (`ruby 2.5.3p105 (2018-10-18 revision 65156) [x... -
03:17 PM Bug #15766 (Closed): Crash in 2.4, 2.5 involving at_exit
- Hello,
I've written a piece of code which reproducibly triggers a crash in some versions of Ruby (2.4 and 2.5, but not 2.2, 2.3 nor 2.6).
As this involves Minitest, I've started by filing a bug report on GitHub:
https://github... - 09:01 PM Revision e3b6c7c7 (git): Import CSV 3.0.8
- This includes performance improvements and backward incompatibility
fixes.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67560 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:25 PM Revision fb96811d (git): Drop obsoleted debugging output [ci skip]
- I confirmed that it's working now in
https://dev.azure.com/rubylang/ruby/_build/results?buildId=396&view=logs&jobId=8c5967c9-8e3a-5773-c80c-34c55d5c3051
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67559 b2dd03c8-39d4-4d8f-98ff-823... - 03:13 PM Revision ad9c5c5d (git): * 2019-04-15
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67558 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- It looks like the old definition was not working as intended...
https://dev.azure.com/rubylang/ruby/_build/results?buildId=394
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67557 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:50 PM Bug #15515 (Closed): OpenStruct raising NoMethodError instead of ArgumentError
- Merged. Thank you for your contribution!
- 01:47 PM Revision 816c5323 (git): OpenStruct: improve error message when passing wrong number of arguments.
- Patch by Lisa Ugray (issue #15515)
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67556 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- it seems not working in
https://dev.azure.com/rubylang/ruby/_build/results?buildId=392
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67555 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67554 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- r67550 introduced the typo
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67553 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67552 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I assumed that ISeq is never GC-ed by `in_jit` + `mjit_mark` on copy job
ISeq, but unfortunately I found SEGV on `mjit_copy_job_handler` in which
iseq->body was somehow Qnil. And it seems to be fixed by disabling the
job when `mjit_free_... -
- $ benchmark-driver benchmark.yml --rbenv='before --jit;after --jit' -v --output=all --repeat-count=12
before --jit: ruby 2.7.0dev (2019-04-14 trunk 67549) +JIT [x86_64-linux]
after --jit: ruby 2.7.0dev (2019-04-14 trunk 67549) +JIT [x86_... -
- as debugged in PR
[close https://github.com/ruby/ruby/pull/2130]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67549 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67548 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- for opt_aref with inline cache to minimize the possibility of JIT cancel.
Also opt_aset and opt_mod are added for the targets.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67547 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67546 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- to prevernt underflow.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67545 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- is defined. It's 0 by default and so it dissappears on actual build.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67544 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:52 AM Revision 57f9a700 (git): Add more debug print for random CI failure on osx Travis
- see r67347
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67543 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:05 AM Revision 3ac518f9 (git): Enabled to some bundler examples again.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67542 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67541 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67540 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- https://github.com/bundler/bundler/commit/a53709556b95a914e874b22ed2116a46b0528852
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67539 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- This reverts commit a1b5d20068a9b1859b383b249e510cd33d196e4a.
Revert "Revert "Skip recompiling tests on i686 Linux""
This reverts commit 7b88a9207b97b94bc3c3be35084c742296f4aff2.
Revert "Simplify matrix for debugging"
This reverts co... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67537 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This reverts commit 19513c88d5f923abb7f226520192aef9f3fcc1c7.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67536 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67535 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67534 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I'm writing `//` comments in newer MJIT code after C99 enablement
(because I write 1-line comments more often than multi-line comments
and `//` requires fewer chars on 1-line) and then they are mixed
with `/* */` now.
For consistency a... -
- somehow they are filing like
https://travis-ci.org/ruby/ruby/jobs/519830085
but they are not so fatal.
Let me just skip them for now and fix tests afterwards.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67532 b2dd03c8-39d4-4d8f-9... - 04:52 AM Revision d6d8fc24 (git): * 2019-04-14
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67531 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- based on inline cache when JIT cancel happens by that.
This feature was in the original MJIT implementation by Vladimir, but on
merging MJIT to Ruby it was removed for simplification. This commit adds
the functionality again for the fol... -
01:12 AM Misc #15459: DevelopersMeeting before/after RubyKaigi2019
- Hi all,
I asked Matz and we fixed dev-meeting schedule:
* 12:00-13:20 door open. I (ko1) will be there with bento-lunch.
* 13:20-13:30 opening
* 13:30-14:00 (1) keyword arguments progress report (mame)
* 14:00-14:30 (2) static c...
04/13/2019
-
10:18 PM Revision 13718651 (git): merge revision(s) 66720:
- separate downloading of Unicode property files and auxiliary files
Separate downloading of Unicode property files in ucd and in ucd/auxiliary.
This is needed because we need information from separate index.html files
... -
- add logic to handle Unicode beta period file names
In downloader.rb, add logic to handle file names of the form
UnicodeData-12.0.0d6.txt. To find the right file, we download
the index of the directory. Then we do... -
- Bump version to date-2.0.0.
I forgot to change it when Ruby 2.6.0 was released.
date_parse.c: extract Japanese era initials
* expand tabs.
date_parse.c: removed 'r' which is not in JIS X 0301 yet
... -
- ruby_2_6 r67525 merged revision(s) 67439,67441,67453,67476.
-
- 03:01 PM Revision d8cac330 (git): * 2019-04-14
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@67526 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- change lib/unicode_normalize/tables.rb to single item per line to make diffs shorter
* template/unicode_norm_gen.tmpl: Change formatting of output to produce only a
single item (or range) for each line to make future d... -
02:10 PM Misc #15459: DevelopersMeeting before/after RubyKaigi2019
- * [Feature #14912] Introduce pattern matching syntax
* I'd like to introduce latest specification, discuss about the details.
-
09:46 AM Misc #15459: DevelopersMeeting before/after RubyKaigi2019
- [Bug #15764] Whitespace and control characters should not be permitted in tokens
(This can and should be easily fixed, but I'd like Matz to give it a check.) -
10:14 AM Misc #15723: Reconsider numbered parameters
- jeremyevans0 (Jeremy Evans) wrote:
> I'm not sure what led you to this statement, as the feature does work with lambdas and methods:
> ...
Hmm, not obvious from description in the accepted feature request. By recent 2.7.0-dev implement... -
10:09 AM Misc #15723: Reconsider numbered parameters
- jeremyevans0 (Jeremy Evans) wrote:
> I'm not sure what led you to this statement, as the feature does work with lambdas and methods:
Well, only with `define_method` methods, not `def` methods, which are the huge majority:
```ruby
... -
08:08 AM Misc #15723: Reconsider numbered parameters
- dunrix (Damon Unrix) wrote:
> Existing solution for example breaks rule of the general approach, as it only works with (anonymous)blocks and procs, not with lambdas and methods which are strict in arguments. It only adds to fragmentatio... -
- Don't you think it may be just the high time stop throwing yet-another of *half-baked hacks* and cease work on implementation & release of the #4475 feature, until other and more mature solution is found ?
It seems the whole concept o... -
- I also think this is a bug. I have changed the category accordingly.
I think we should restrict the characters usable in identifiers to some reasonable ranges. I agree that we mainly want to focus on ASCII programs, but we should do a... -
06:18 AM Bug #15764: Whitespace and control characters should not be permitted in tokens
- I am not sure this is a bug, though. If it is a valid Unicode token then it should
work, so the behaviour would seem correct to me. Actually sawa made a similar comment
on SO - he is very active on the ruby bug tracker here too. :-)
... -
- ruby_2_6 r67524 merged revision(s) 67497,67498.
-
- ext/openssl/ossl_bn.c (ossl_bn_initialize): get rid of SEGV
OpenSSL::BN.new(nil, 2) dumped core.
[ruby-core:92231] [Bug #15760]
* expand tabs.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@6752... -
- This reverts commit 30f71f4768e0babc60f5be6ca235d2c40268bc27.
I've also overlooked we're doing RESTORE_REGS()...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67523 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- When reviewing r66565, I overlooked that `GET_ISEQ()` and `GET_EP()` are
NOT `ec->cfp->iseq` and `ec->cfp->ep` but `reg_cfp->iseq` and
`reg_cfp->ep`.
`vm_push_frame` updates `ec->cfp` and in this case we want to check the
callee's cfp a... -
- nobu (Nobuyoshi Nakada) wrote:
> No error occurred, maybe OpenSSL headers have changed since the previous build?
> ...
I'm not sure why, but this seems to have worked. Thanks a lot! -
05:19 AM Bug #15670: Ripper treats :"sym" as xstring
- This change broke a library preval https://github.com/kddeisz/preval/issues/1, and potentially also breaks other libraries that uses Ripper. Since this is an incompatible change for Ripper.sexp, I guess backport requires a loud changelog...
- 12:56 AM Revision e7f7aa87 (git): * 2019-04-13
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67521 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 12:56 AM Revision a73dae4c (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67520 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 12:56 AM Revision d3da5fbd (git): Proc.new: change deprecation warning for clarity (issue #15539)
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67519 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:46 AM Bug #12548: Rounding modes inconsistency between round versus sprintf
- I came across this thread now, because I've noticed that sprintf's behavior has actually changed in Ruby 2.4 too, just... not the same way as round's did...
```
> echo "n = [5.005, 5.015, 5.025]; puts 'round: ' + n.map { |x| x.round(...
04/12/2019
-
- Sorry I missed this.
I'm positive on this patch and will commit it shortly unless there's any objection. -
- jeremyevans0 (Jeremy Evans) wrote:
> The behavior changes if `foo` is a local variable:
> ...
Good catch, I forgot about that case.
Indeed, that's confusing.
This case can be worked around with parentheses if there is a local variab... -
- Eregon (Benoit Daloze) wrote:
> headius (Charles Nutter) wrote:
> ...
The behavior changes if `foo` is a local variable:
```ruby
foo = 1
proc{foo &1}.call
# => 1
proc{foo & 1}.call
# => 1
```
This proposal has the followin... -
- headius (Charles Nutter) wrote:
> Conflicts with bitwise AND, doesn't it?
No, binary operators already care about spacing to clarify which one it is, and this syntax "conflict" already exists anyway:
~~~ ruby
irb(main):001:0> cl... -
08:10 PM Misc #15723: Reconsider numbered parameters
- > Another idea for syntax, already mentioned in https://bugs.ruby-lang.org/issues/4475#note-12 : &1, &2, etc.
Conflicts with bitwise AND, doesn't it?
```ruby
foo &1
```
Is it `foo() & 1` or `foo(&1)`? -
- Another idea for syntax, already mentioned in https://bugs.ruby-lang.org/issues/4475#note-12 : &1, &2, etc.
`&` associates much better with blocks than `@`: `map(&:name)`, `foo(&block)`, etc.
In fact, I think many previous suggestion... -
- Oh, another simplication... if user code in 2.7+ attempts to read `_1` before writing it in a block, that can be an indication that it's expected to be an argument offset. If it's assigned first it's just a normal local variable.
-
- What about using `_1`, `_2`? These are value variable names that could be reserved for argument offsets. This would mimic some golfed block code like `{|_| ...}` (though I know there's some debate about whether `@1` should map to `|x|` o...
-
- mame (Yusuke Endoh) wrote:
> However, akr and I think that "2.7 is completely compatible with 2.6 except warnings" approach is not good enough. We need to provide a migration path that allows users to rewrite their code for 3.0 gradual... -
01:52 PM Feature #14183: "Real" keyword argument
- @jeremyevans0,
You registered this ticket for pre-RubyKaigi [Misc#15459]. Do you have an idea how to discuss the issue?
@ko1 is now creating an agenda, and maybe 30 minutes will be allotted to this issue. The agenda is not decide... -
- Jeremy, thank you for working on this issue.
> I believe the expected behavior in Ruby 2.7 is to warn but return the same results as Ruby 2.6 in all three cases, is that correct?
I had intended the incompatibility, as I said in "Mi... - 02:32 PM Revision 95a82766 (git): * 2019-04-12
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67518 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:32 PM Revision 39b04bc6 (git): [DOC] Add `ifnone` example to `find` documentation [ci skip]
- [Fix GH-2110]
From: OKURA Masafumi <masafumi.o1988@gmail.com>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67517 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
09:59 AM Bug #15708: Implicit numbered argument decomposes an array
- jeremyevans0 (Jeremy Evans) wrote:
> Attached is a patch that will turn off destructuring if the only implicit block variable is `@1`:
```diff
- args->nd_ainfo->rest_arg = excessed_comma;
+ if (max_numparam > 1) {
+ args->nd_a... -
04:17 AM Feature #15765: [PATCH] Module#name without global constant search
- This is for #11119 and #15625.
-
- Hello!
The current implementation of `Module#name` is known for having sub-optimal performance when it comes to anonymous modules. (see #11119 and #15625)
I have put together a reimplementation of `Module#name`, which works by eagerl... -
- * new built-in class/method definition features in Ruby and C (will be talked at RubyKaigi 2019, my talk) (ko1)
04/11/2019
-
11:16 PM Bug #15300: rb_frame_method_id_and_class deprecated in 2.6
- I just noticed that Rice works perfectly under Ruby 2.6.2! Thank you so much.
-
- Attached is a patch that will turn off destructuring if the only implicit block variable is `@1`:
```ruby
# equivalent to proc{|x| x}
proc{@1}.call([1,2])
# => [1, 2]
# equivalent to proc{|_,x| x}
proc{@2}.call([1,2])
# => 2
... -
08:59 PM Bug #15764 (Assigned): Whitespace and control characters should not be permitted in tokens
- As of Ruby 2.5.1p57, it appears that all valid Unicode code-points above 128 are permitted in tokens. This includes whitespace and control characters.
This was demonstrated here: https://gist.github.com/qrohlf/7045823
I have attach... -
03:17 PM Bug #15360: "ThreadError: deadlock; recursive locking" error when recursive lock shouldn't be possible
- `git bisect` shows the problem occurs frequently since r58604.
But I don't know it can occur before the commit.
https://bugs.ruby-lang.org/projects/ruby-trunk/repository/trunk/revisions/66489/entry/thread_sync.c#L267
`do_mutex_lock(... -
- ruby_2_6 r67516 merged revision(s) 67466.
-
- enumerator.c: force hash values fixable
* enumerator.c (arith_seq_hash): force hash values fixable on
LLP64 environment. [ruby-core:92190] [Bug #15755]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@67... -
- ruby_2_6 r67515 merged revision(s) 67467.
-
- range.c: force hash values fixable
* range.c (method_hash): force hash values fixable on LLP64
environment. [ruby-core:92191] [Bug #15756]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@67515 b2dd03c8-... -
- ruby_2_6 r67514 merged revision(s) 67468.
-
- range.c: force hash values fixable
* range.c (range_hash): force hash values fixable on LLP64
environment. [ruby-core:92194] [Bug #15757]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_6@67514 b2dd03c8-3... - 10:36 AM Revision 6f866fd9 (git): * 2019-04-11
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67513 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67512 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Fix GH-2115]
From: Lourens Naudé <lourens@bearmetal.eu>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67511 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
09:33 AM Misc #15723: Reconsider numbered parameters
- I very much like the feature itself, esp. for one liners you can come up with on a pry prompt. What I very much dislike though is the use of `@` which is a glorious hack if there is any since currently `@` tokenizably resolves to 'instan...
-
07:04 AM Bug #15761: File::Statfs documentation still exists on ruby-doc.org/core-trunk/
- Sorry, I didn't notice it's not official.
I'll report to them.
I didn't know docs.ruby-lang.org is a thing, it never shows up in Google search, maybe it needs some SEO.
Thanks for the reply!
 -
06:53 AM Bug #15746: 11 test cases run failed
- nobu (Nobuyoshi Nakada) wrote:
> Run with `make test-all` or test/runner.rb:
> ...
Thanks! -
- This might be the same issue as:
* https://bugs.ruby-lang.org/issues/15490
* https://bugs.ruby-lang.org/issues/15639
* https://github.com/hanami/hanami/issues/993
The common points are:
* macOS (darwin17 or 18)
* uses multipl... -
01:37 AM Bug #15763: Segmentation fault in timeout.rb / sleep
- Additionally, the issue does not seem to happen on every build. If I rebuild the same version of ruby, the issue may go away. (until another few rebuilds)
-
- I'm running into crashes on both ruby 2.6.1 and 2.6.2 (2.5.x is all good).
I'm on OSX / mojave with ruby installed via rbenv / ruby-build. Confirmed on two different machines.
The crash happens through the parallel gem, but it happen...
04/10/2019
-
- http://documenting-ruby.org is dead project.
Can you report ruby-doc.org administrator? Its website is not an official document resource. -
- Please report at http://documenting-ruby.org.
-
- Agree that it is confusing.
In my opinion, if it were easily possible so, it would be best to have only one
central repository including the documentation, e. g. something like
doc.ruby-lang.org or a sub-page like that.
As it is ... -
- Hi
I found File::Statfs still exists in core-trunk web documentation.
But this feature no longer exists.
http://ruby-doc.org/core-trunk/File/Statfs.html
Google search leads me to this page, which is a bit confusing. -
06:17 PM Bug #15360: "ThreadError: deadlock; recursive locking" error when recursive lock shouldn't be possible - Is there a plan to fix this? We have been noticing this bug occasionally in production.
-
- No error occurred, maybe OpenSSL headers have changed since the previous build?
Could you try `make -C ext/openssl clean`? -
- This is an error that only showed up today. I have been able to compile without problems on Cygwin until very recently. The only file recently changed in ext/openssl seems to be:
https://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/ext/op... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67510 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67509 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67508 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- trying to fix
https://dev.azure.com/rubylang/ruby/_build/results?buildId=363
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67507 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- OpenSSL::BN.new(nil, 2) dumped core.
[ruby-core:92231] [Bug #15760]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67506 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67505 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67504 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * parse.y (rb_parser_fatal): fix "parser" in the message which was
replaced accidentally. it is not the argument name.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67503 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67502 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 09:16 AM Revision 37994bc5 (git): * 2019-04-10
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67501 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 09:16 AM Revision 481481b8 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67500 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Because hard to specify commits related to r67479 only.
So please commit again.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67499 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Applied in changeset trunk|r67497.
----------
ext/openssl/ossl_bn.c (ossl_bn_initialize): get rid of SEGV
OpenSSL::BN.new(nil, 2) dumped core.
[ruby-core:92231] [Bug #15760] -
- ext/openssl/ossl_bn.c
```
221 if (!BN_bin2bn((unsigned char *)StringValuePtr(str), RSTRING_LENINT(str), bn)) {
222 ossl_raise(eBNError, NULL);
223 }
224 break;
```
This code depends on t... - 08:03 AM Revision 0cc2ffbc (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67498 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- OpenSSL::BN.new(nil, 2) dumped core.
[ruby-core:92231] [Bug #15760]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67497 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67496 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67495 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * vm_method.c (rb_add_method_iseq): use rb_method_iseq_t, as
rb_method_definition_set refers, with a cast to suppress a
warning.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67494 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67493 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Ruby includes rubygems, but this is imported, see e.g. https://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=67415. So improvements to rubygems should be proposed and discussed upstreams.
-
- I can not speak for the ruby core team; it may be best to actually ask matz directly,
but let's ignore this for the moment. I think, viewed objectively, there would be no
reason to avoid/ignore Rust. Ruby's primary internal focus is on... -
02:37 AM Feature #15759: Support Rust/Cargo in Gem::Ext::Builder
- ### Notable Gems using Rust
1. https://github.com/danielpclark/faster_path
2. https://github.com/ianks/fast_woothee -- shameless plug
3. https://github.com/tildeio/helix -- a framework for building Rust extensions
4. https://github... -
- Over the past few years, Rust has proven to be an incredibly stable and accessible option for those wishing to write native extensions for Ruby. Rust is particularly well-suited for Ruby for a few reasons:
1. Integration is straight-... -
- * parse.y (rb_parser_fatal): fix "parser" in the message which was
replaced accidentally. it is not the argument name.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67492 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67491 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67490 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
04/09/2019
-
11:48 PM Revision d099eabb (git): Set a write barrier between iseq and mark objects
- ISeq pins references in the mark array during compile, so it manually
marks references in the mark_ary. This was causing write barrier
misses, so we need to add a write barrier when pushing on the mark
array.
git-svn-id: svn+ssh://ci.r... -
11:35 PM Feature #15594 (Closed): [PATCH] net/imap: support SNI
- Applied in changeset trunk|r67488.
----------
Support SNI
This fixes connecting using TLS 1.3 to imap.gmail.com
[Fix GH-2077] [Feature #15594]
From: Marc-Antoine Perennou <Marc-Antoine@Perennou.com> -
11:27 PM Feature #15594: [PATCH] net/imap: support SNI
- Here's a possible workaround:
```ruby
require 'net/protocol'
class Net::Protocol
module ForceSNI
def ssl_socket_connect(*)
@sock.hostname = @host if @sock.respond_to? :hostname=
super
end
end
pre... -
- Maybe POP3 & SMTP need this too.
-
- I think this is necessary for the library to be able to connect to the Gmail server which now requires SNI.
-
- This fixes connecting using TLS 1.3 to imap.gmail.com
[Fix GH-2077] [Feature #15594]
From: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67488 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67487 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67486 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Weak map references can't move because the st_table needs their address
as a key. But, we also need to remove T_NONE from the map so they
aren't reused.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67485 b2dd03c8-39d4-4d8f-98ff-82... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67484 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- JSON gem is referencing constants defined in Ruby then keeping a
reference as a global. We need to register these globals so they stay
pinned.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67483 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- This commit tries to make compaction more likely by allocating some
objects and then throwing them away
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67482 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Applied in changeset trunk|r67479.
----------
Adding `GC.compact` and compacting GC support.
This commit adds the new method `GC.compact` and compacting GC support.
Please see this issue for caveats:
https://bugs.ruby-lang.org/issue... -
- Hi,
Here are some statistics I gathered. I'll present a few more at RubyKaigi using our application.
https://gist.github.com/tenderlove/99112e9fcc85d9c6c7d9d0ea40063fc6 - 08:32 PM Revision ca9733dc (git): * 2019-04-10
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67481 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 08:32 PM Revision 2d912017 (git): * properties.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67480 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This commit adds the new method `GC.compact` and compacting GC support.
Please see this issue for caveats:
https://bugs.ruby-lang.org/issues/15626
[Feature #15626]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67479 b2dd03c8-39d... -
- FWIW, the replies on my tweet above is some good sign that very few Rubyists expect this behavior and it breaks the basics assumptions of how the feature can be used.
-
- For some reason, a reply on the tracker seems to have been lost, or removed.
I think it is highly relevant, so I'll quote it here:
sholden (Scott Holden) wrote:
> This is definitely not the behavior I would expect. In everything tha... -
03:18 PM Bug #15708: Implicit numbered argument decomposes an array
- This is what happens when one syntactic sugar(*) collides with another.
(*) `a.map { |x,| x }` being a shorthand for `a.map { |(x)| x }` , and sometimes not, depending on the runtime values.
Neither of these are good, IMO (one for ... -
- * NEWS: [DOC] markup command line options, not to convert
successive hyphens to an en-dash unintentionally.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67478 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * NEWS: [DOC] fold lines not to make the BTS refereces wrong
links, without a backslash.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67477 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Run with `make test-all` or test/runner.rb:
```
$ make test-all TESTS=test_extlibs.rb TESTOPTS=-v
../src/revision.h unchanged
Run options: "--ruby=./miniruby -I../src/lib -I. -I.ext/common ../src/tool/runruby.rb --extout=.ext -- ... -
- nobu (Nobuyoshi Nakada) wrote:
> Run these tests under the build tree.
Hi,
I don't think this is problem where I run the test. Can you explain more? Thanks.
Besides, I run the test on target since cross compile.
1. for error l... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67476 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
07:39 AM Misc #15723: Reconsider numbered parameters
- Marc, okay, I agree with you. But if not in the form of `&:first` or `&:last`, I still frequently see the methods `first` and `last` used in blocks, and I see that those can be accessed as `_.first`, `_.last` according to your proposal, ...
-
- I have updated my branch (https://github.com/jeremyevans/ruby/commits/keyword-argument-separation) to restore backwards compatibility for methods using keyword arguments when calling with a final positional hash with mixed Symbol and non...
-
- Applied in changeset trunk|r67474.
----------
date: support for Reiwa, new Japanese era
[Feature #15742] - 01:27 AM Revision 49255fd7 (git): * 2019-04-09
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67475 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Feature #15742]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67474 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67473 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
04/08/2019
-
- akr (Akira Tanaka) wrote:
> > Maybe, we should await next JIS X 0301?
> ...
As Japanese government has claimed that only one month is enough for the transition, the new standard will be issued in this month at latest :) -
05:34 AM Feature #15742: Add Date#jisx0301 support new Japanese era
- - Unicode CLDR 35.1 alpha uses "R".
https://www.unicode.org/repos/cldr/tags/release-35-1-alpha/common/main/ja.xml
- OpenJDK also uses "R".
https://bugs.openjdk.java.net/browse/JDK-8205432
http://hg.openjdk.java.net/jdk/jdk/rev/... -
- sawa (Tsuyoshi Sawada) wrote:
> Marc, regarding `|x, |`, I see plenty of cases like `map(&:first)` (or `map(&:last)`). Probably taking care of these cases is more important than the explicit `|x, |` cases. If you are going to count, you... -
07:17 PM Misc #15723: Reconsider numbered parameters
- Eregon (Benoit Daloze) wrote:
> @sawa Thank you for think link, I missed that issue.
> ...
Even more confusion ahead.
I don't see that this feature adds any benefit besides saving some chars in an ideal case.
On the downside it wil... -
- @sawa Thank you for think link, I missed that issue.
I stand by my opinion though, and expressed it there too. -
- Eregon (Benoit Daloze) wrote:
> @sawa The `|x,|` behavior for `@1` can only be considered a bug. It prevents `array_of_arrays.each { p @1 }` to work correctly.
> ...
@Eregon I think you better check the relevant threads before dumping ... -
- FWIW, I would bet >99% of Rubyists would agree this is a bug: https://twitter.com/eregontp/status/1115318993299083265
-
- As I said in #15723,
I believe the `|x,|` behavior for `@1` can only be considered a bug.
It prevents `array_of_arrays.each { p @1 }` to work correctly.
Why would we want to prevent that and make this pattern not general, dangerou... -
- As to commits, see:
r64620 - Declare as gnu_printf on mingw
https://github.com/ruby/ruby/commit/c115b39e033979bac7cfd2db5735549430dc14f7
and
r64630 - use mingw ANSI stdio
https://github.com/ruby/ruby/commit/1cf2bb4b20857581125... -
- @nobu
Thanks for the reply. Stupid on my part, I overlooked the changes re `gnu_printf` in configure.ac, and it's compiling fine.
I found the patch for it looking in an old copy of ruby-loco (using 'makepkg'). Back when Appveyor ... -
- `PRI_LL_PREFIX` should be defined in config.h by configure.ac.
```sh
$ grep '#define PRI_LL_PREFIX' .ext/include/x64-mingw32/ruby/config.h
#define PRI_LL_PREFIX "I64"
``` -
- Applied in changeset trunk|r67472.
----------
object.c: fix searching nested const paths
* object.c (rb_mod_const_get, rb_mod_const_defined): nested const
paths should not search from toplevel constants.
[ruby-core:92202] [Bug #15758] -
11:30 AM Bug #15758 (Closed): Object.const_defined?(name) falsely returns true on classes that are not defined
- in short https://i.imgur.com/qvIIBuu.png
Object.const_defined?('Baz::Bar') -> true
yet Baz::Bar -> class not found!
test to run, all ok on ruby 2.6.0, bug in 2.6.2
~~~ruby
class Foo
end
class Bar
end
class Baz
cla... -
- * object.c (rb_mod_const_get, rb_mod_const_defined): nested const
paths should not search from toplevel constants.
[ruby-core:92202] [Bug #15758]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67472 b2dd03c8-39d4-4d8f-98ff-823fe6... -
- * test/ruby/test_module.rb (TestModule#test_nested_get): fix a
typo. nested module's name is a qualified path.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67471 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- shevegen (Robert A. Heiler) wrote:
> But having a situation where changes to MRI could possibly be delayed due to difficulties
> ...
I am not proposing anything like that.
Practically, whenever MRI decides to add an experimental featu... -
- naruse (Yui NARUSE) wrote:
> Web browsers showed us that it cannot achieve at once both experimental and portable.
I will dare to challenge that.
Why would `ExperimentalFeatures.resolve_feature_path` not be portable?
Portable here ... -
- One worry that I have here is that this change may add bureaucratic overhead to MRI in
particular. I have nothing against alternative ruby implementations at all, quite the
opposite - the easier it is to implement ruby/rubies the bette... -
- Web browsers showed us that it cannot achieve at once both experimental and portable.
-
- ioquatix (Samuel Williams) wrote:
> I think it's a good idea. Might I suggest two potential ideas?
Go ahead :)
> ...
This is equivalent to my proposition of `ExperimentalFeatures` with a different name, right?
I don't understan... -
01:26 AM Feature #15752: A dedicated module for experimental features
- I think it's a good idea. Might I suggest two potential ideas?
Firstly, maybe have a shared `Ruby` module for common but interpreter specific functionality.
Then, interpreter specific modules e.g. `CRuby`, `MRuby`, `JRuby`, `Truffl... -
- Run these tests under the build tree.
-
- As far as I remember, the name "RubyVM" is introduced because the name of the implementation which is called as CRuby or MRI cannot be decided, and also its VM's name is not actually YARV. To rename it to something, it needs to reopen th...
-
- * struct.c (rb_struct_hash): force hash values fixable on LLP64
environment.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67470 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I **STRONGLY** object removal of flip-flop, in "-e" option at least.
It is too tiresome to rewrite with a flag variable in one-liners. -
- Applied in changeset trunk|r67468.
----------
range.c: force hash values fixable
* range.c (range_hash): force hash values fixable on LLP64
environment. [ruby-core:92194] [Bug #15757] -
02:36 AM Bug #15757 (Closed): [BUG] Unnormalized Fixnum value on Range#hash.to_s on Windows
- To reproduce:
```
ruby -e "(0..1).hash.to_s"
```
Result:
```
-e:1: [BUG] Unnormalized Fixnum value 0x8fa800e97a8f86b7
ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
-- Control frame information ------------------... -
- Applied in changeset trunk|r67467.
----------
range.c: force hash values fixable
* range.c (method_hash): force hash values fixable on LLP64
environment. [ruby-core:92191] [Bug #15756] -
- To reproduce:
```
ruby -e "method(:p).hash.to_s"
```
Result:
```
-e:1: [BUG] Unnormalized Fixnum value 0xd258e532a3942665
ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
-- Control frame information --------------... -
- Applied in changeset trunk|r67466.
----------
enumerator.c: force hash values fixable
* enumerator.c (arith_seq_hash): force hash values fixable on
LLP64 environment. [ruby-core:92190] [Bug #15755] -
- To reproduce:
```
ruby -e "0.step.hash.to_s"
```
Result:
```
-e:1: [BUG] Unnormalized Fixnum value 0xb3735f03e7a21893
ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
-- Control frame information ------------------... - 03:26 AM Revision b29f55c5 (git): * 2019-04-08
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67469 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * range.c (range_hash): force hash values fixable on LLP64
environment. [ruby-core:92194] [Bug #15757]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67468 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * range.c (method_hash): force hash values fixable on LLP64
environment. [ruby-core:92191] [Bug #15756]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67467 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * enumerator.c (arith_seq_hash): force hash values fixable on
LLP64 environment. [ruby-core:92190] [Bug #15755]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67466 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I believe this is the same issue as #12717. We are trying to address this issue in #14183.
-
- I have updated my GitHub branch (https://github.com/jeremyevans/ruby/commits/keyword-argument-separation) to fix the issues in mame's branch that I identified in my previous comment.
Now, my branch keeps compatibility with Ruby 2.6 in...