aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bump patchlevel to 125nagachika2020-09-151-2/+2
|
* Merge RubyGems 3.1.4Hiroshi SHIBATA2020-09-1526-119/+372
|
* spec/ruby/core/file/utime_spec.rb: far future timestamp may be trancatedYusuke Endoh2020-09-092-5/+7
| | | | | | | | | | | | | | | | | | Under some Ext4 filesystem settings, a timestamp is limited up to 0x37fffffff (2446-05-10). https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Timestamps > Therefore, timestamps should not overflow until May 2446. Actually the spec fails under one of our CI environments, like: ``` 1) File.utime allows Time instances in the far future to set mtime and atime FAILED Expected 2446 == 559444 to be truthy but was false ``` https://rubyci.org/logs/rubyci.s3.amazonaws.com/arch/ruby-master/log/20200208T180002Z.fail.html.gz
* Run a TracePoint test in an insolated processnagachika2020-09-072-9/+11
| | | | | to prevent a random failure like http://ci.rvm.jp/results/trunk-random2@phosphorus-docker/3024287
* * 2020-09-07 [ci skip]git2020-09-071-1/+1
|
* Fix a random test failure by TracePointnagachika2020-09-071-2/+4
| | | | | | | A test worker process may already be enabling TracePoint, which results in changing the insn name in this test. http://ci.rvm.jp/results/trunk-random0@phosphorus-docker/3022750
* merge revision(s) ff5e66034006a875125581114cce19d46843b32a: [Backport #17015]nagachika2020-09-063-2/+19
| | | | | Added `NODE_SPECIAL_EXCESSIVE_COMMA` info to `ARGS` of `RubyVM::AbstractSyntaxTree`.
* merge revision(s) 3e02cd518fbe4d91c2aca7fbc3c5aafa387d3cb7: [Backport #17149]nagachika2020-09-064-3/+21
| | | | | | | | Trace :return of builtin methods using opt_invokebuiltin_delegate_leave insn. Since Ruby 2.7, :return of methods using builtin have not been traced properly.
* merge revision(s) 11963da9e8e98821860fbb0c0f2adc118860c814: [Backport ↵nagachika2020-09-063-3/+9
| | | | | | | | #16603] [Backport #17141] Check type of empty keyword [Bug #16603] Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
* bump patchlevel to 119nagachika2020-09-051-3/+3
|
* Revert "Don't display singleton class in Method#inspect unless method ↵nagachika2020-09-053-34/+1
| | | | | | | | defined there" [Backport #16771] This reverts commit 0d24fb774d84d4a99454ce10fd343da00049a588.
* merge revision(s) 8e189df32cacef4b21e357a590d349330532baf5: [Backport #17013]nagachika2020-08-073-3/+15
| | | | Add operator info to `OP_ASGN2` of `RubyVM::AbstractSyntaxTree`.
* merge revision(s) d05f04d27dd86c67e4a8dfff4392f806cf577bdf: [Backport #16931]nagachika2020-08-013-2/+3
| | | | | | | | Fixed `defined?` against protected method call Protected methods are restricted to be called according to the class/module in where it is defined, not the actual receiver's class. [Bug #16931]
* Split test_defined_methodNobuyoshi Nakada2020-08-011-1/+22
|
* Fix typo in test namePeter Zhu2020-08-011-1/+1
|
* Test for [Bug #16669]Nobuyoshi Nakada2020-08-011-0/+8
|
* Split test_definedNobuyoshi Nakada2020-08-011-2/+16
|
* bump up patchlevel for a332e8a0ddad90c540c6c52f0db2a45e5955a23dnagachika2020-08-011-3/+3
|
* ruby_2_7 update MinGW Actions workflowMSP-Greg2020-08-011-4/+3
|
* merge revision(s) 1b4d406e3a04032b6d01e92b6d184a16945c6ac3: [Backport ↵nagachika2020-07-263-5/+16
| | | | | | | | #16498] [Backport #16914] Hash#transform_values should return a plain new Hash [Bug #16498]
* partially merge revision adf709a78534c1483ba851ccb0490464ca31503c: [Backport ↵nagachika2020-07-263-14/+21
| | | | | | | | | | | | #16801] Classes made from Struct should have default new singleton method. Co-authored-by: Yusuke Endoh mame@ruby-lang.org Co-authored-by: John Hawthorn john@hawthorn.email Co-authored-by: Adam Hess HParker@github.com Co-authored-by: Jose Cortinas jacortinas@gmail.com Co-authored-by: Jean Boussier jean.boussier@gmail.com
* merge revision(s) ↵nagachika2020-07-2619-14/+32
| | | | | | | | | | | | | | | | | | | | a0bc3f2a1c2c98f225612101cb4e1ea1a6813546,75a0447c15a7ab017bd4240c2a9cc69b134b80b9,f1699314147bad2cf5550cc582693424fdbc2510: [Backport #16846] Suppress C4267 "possible loss of data" warnings Suppress C4267 "possible loss of data" warnings Just cast down explicitly. win32ole: separate global variable declarations and definitions https://gcc.gnu.org/gcc-10/changes.html#c > * GCC now defaults to `-fno-common`. As a result, global > variable accesses are more efficient on various targets. In > C, global variables with multiple tentative definitions now > result in linker errors. With `-fcommon` such definitions are > silently merged during linking.
* merge revision(s) 5e81e8675a020ecd493620a4ff38db8fcf4b972a: [Backport #16780]nagachika2020-07-252-9/+9
| | | | | | Ignore exceptions when closing data connections [Bug #16780] Patch by koshigoe (Masataka SUZUKI). Thanks!
* merge revision(s) cbe4f75ef802f13d05f94e42274b65a062bd3666: [Backport #16834]nagachika2020-07-253-8/+36
| | | | | | | | Fix rb_profile_frame_classpath to handle module singletons Right now `SomeClass.method` is properly named, but `SomeModule.method` is displayed as `#<Module:0x000055eb5d95adc8>.method` which makes profiling annoying.
* merge revision(s) 71c166e11e761dcaaa943f9b94da38f86ada1bdb: [Backport #16854]nagachika2020-07-253-6/+8
| | | | Fixed argument forwarding in reserved word method [Bug #16854]
* merge revision(s) 08529a61153e5c40f57a65272211357511d6e6db: [Backport #16798]nagachika2020-07-253-4/+22
| | | | Compare environment variable names in those manor [Bug #16798]
* merge revision(s) 2f1895fa15386fb3cdc91c5604171290828b9da8: [Backport #16767]nagachika2020-07-253-2/+11
| | | | Fixed formatted substring expansion [Bug #16767]
* merge revision(s) 927308108cced69cae478798004524b9a5d2f252: [Backport #16764]nagachika2020-07-233-9/+33
| | | | Fix source location of autoloaded constant [Bug #16764]
* merge revision(s) da05c1552ee519d8f180b48d97148d28501acb35: [Backport #16749]nagachika2020-07-233-8/+5
| | | | Update to ruby/spec@cc7b9e5
* merge revision(s) 72c02aa4b79731c7f25c9267f74b347f1946c704: [Backport #16662]nagachika2020-07-233-91/+8
| | | | | | | Moved not-implemented method tests [Bug #16662] Test not-implemented method with the dedicated methods, instead of platform dependent features.
* merge revision(s) b23fd59cbb3f097bcd559d0c85a86ff7a1eeeb7e: [Backport #16501]nagachika2020-07-233-8/+60
| | | | | | | | | | | | | | | marshal.c: Support dump and load of a Hash with the ruby2_keywords flag It is useful for a program that dumps and load arguments (like drb). In future, they should deal with both positional arguments and keyword ones explicitly, but until ruby2_keywords is deprecated, it is good to support the flag in marshal. The implementation is similar to String's encoding; it is dumped as a hidden instance variable. [Feature #16501]
* Get rid of use of magic number 'E'Nobuyoshi Nakada2020-07-231-4/+10
|
* merge revision(s) e04418bb16cd99b4a4402e7457d3bdc967284f98: [Backport #16830]nagachika2020-07-233-1/+6
| | | | | | | | [ruby/uri] Check if DN exists https://bugs.ruby-lang.org/issues/16830 https://github.com/ruby/uri/commit/b4bf8c1217
* merge revision(s) a2be428c5fec31b8adbd5ac087e7637ddf7e54d0: [Backport #16826]nagachika2020-07-232-5/+13
| | | | | | Fix ObjectSpace::WeakMap#key? to work if the value is nil * Fixes [Bug #16826]
* merge revision(s) 579645d9f870fa4116dcd3200bbbb6e2c0b7f400: [Backport #17033]nagachika2020-07-233-2/+26
| | | | Fixed infinite loop at error in printing cause [Bug #17033]
* merge revision(s) 99a9c3fe2eaab8157765d792dc871da6daea0327: [Backport #17024]nagachika2020-07-234-6/+17
| | | | Fixed yday and wday with timezone [Bug #17024]
* merge revision(s) 2ecfb88ee50510955acd3ae9fc94a5f109e7f109: [Backport #16918]nagachika2020-07-233-2/+13
| | | | | | | | | Correctly remove temporary directory if path yielded is mutated Another approach would be to freeze the string, but that could cause backwards compatibility issues. Fixes [Bug #16918]
* merge revision(s) ↵nagachika2020-07-233-4/+74
| | | | | | | | | | 5a79d8e0507cd143100bf928a88a59a8b5a5bca6,160511d851375f7cb922faae3a9310633187f51f: [Backport #16925] Fix error raised by Net::HTTPResponse#inflater if the block raises * See https://bugs.ruby-lang.org/issues/13882#note-6 Quarantine specs which fail frequently with CHECK_LEAKS=true
* merge revision(s) ↵nagachika2020-07-193-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bf1a6771f305ea286a3ae575676924551c03e857,c1463625555b061a2b94c3b6c5581730b482a285: [Backport #17012] [Backport #17014] Fix non-numeric exclusive Range#minmax bug The implementation of Range#minmax added in d5c60214c45 causes the following incorrect behaviour: ('a'...'c').minmax => ["a", ["a", "b"]] instead of ('a'...'c').minmax => ["a", "b"] This is because the C implementation of Range#minmax (range_minmax) directly delegates to the C implementation of Range#min (range_min) and Range#max (range_max), without changing the execution context. Range#max's C implementation (range_max), when given a non-numeric exclusive range, delegates to super, which is meant to call Enumerable#max. However, because range_max is called directly by range_minmax, super calls Enumerable#minmax instead, causing the incorrect nesting. Perhaps it is possible to change the execution context in an optimized manner, but the simplest solution seems to be to just explicitly delegate from Range#minmax to Range#min and Range#max. Use static variables in Range#minmax
* merge revision(s) 0ba27259d390e902139c0e2e94b9d18ef227748e: [Backport #16940]nagachika2020-07-192-3/+4
| | | | | | | | | Fix crashes in the peephole optimizer on OpenBSD/sparc64 These crashes are due to alignment issues, casting ADJUST to INSN and then accessing after the end of the ADJUST. These patches come from Stefan Sperling <stsp@apache.org>, who reported the issue.
* merge revision(s) 6e7e7c1e577d6c2276e9a8cc85c28c55c46c2618: [Backport #17023]nagachika2020-07-192-2/+2
| | | | | | | | | | | | | | | | Only marked objects should be considered movable Ruby's GC is incremental, meaning that during the mark phase (and also the sweep phase) programs are allowed to run. This means that programs can allocate objects before the mark or sweep phase have actually completed. Those objects may not have had a chance to be marked, so we can't know if they are movable or not. Something that references the newly created object might have called the pinning function during the mark phase, but since the mark phase hasn't run we can't know if there is a "pinning" relationship. To be conservative, we must only allow objects that are not pinned but also marked to move.
* merge revision(s) 26c179d7e7e7ae0eb21050659c3e8778358230ab: [Backport #17026]nagachika2020-07-193-2/+13
| | | | | | | | | | Check argument to ObjectSpace._id2ref Ensure that the argument is an Integer or implicitly convert to, before dereferencing as a Bignum. Addressed a regression in b99833baec2. Reported by u75615 at https://hackerone.com/reports/898614
* bump patchlevel to 93nagachika2020-07-181-2/+2
|
* Update some syslog tests to absurb the format change of FreeBSD syslogYusuke Endoh2020-07-183-10/+10
| | | | | | | | | | | | | | | | | | FreeBSD ``` $ ruby -rsyslog -e 'Syslog.open("rubyspec", Syslog::LOG_PERROR) {|s| s.log(Syslog::LOG_ALERT, "Hello") }' rubyspec 78462 - - Hello ``` Linux ``` $ ruby -rsyslog -e 'Syslog.open("rubyspec", Syslog::LOG_PERROR) {|s| s.log(Syslog::LOG_ALERT, "Hello") }' rubyspec: Hello ``` https://github.com/freebsd/freebsd/commit/591ef7c8076109cff3c41f9bb50da996a34121e9
* test/openssl/test_ssl: skip test_fallback_scsv if necessaryKazuki Yamaguchi2020-07-181-0/+4
| | | | | | | | Run the test case only when the OpenSSL supports both TLS 1.1 and TLS 1.2. Note that the fallback SCSV mechanism is for TLS 1.2 or older and not for 1.3. Fixes: https://github.com/ruby/openssl/issues/336
* test/lib/jit_support.rb: Let JIT tests skip on centos8Yusuke Endoh2020-07-111-0/+2
| | | | It has the same issue as RHEL 8. k0kubun said he will fix later
* OpenSSL 1.1.1 introduces a new '.include' directive. Update our confignagachika2020-07-113-20/+92
| | | | | | | | | | | | | | | | parser to support that. As mentioned in the referenced GitHub issue, we should use the OpenSSL API instead of implementing the parsing logic ourselves, but it will need backwards-incompatible changes which we can't backport to stable versions. So continue to use the Ruby implementation for now. References: https://github.com/ruby/openssl/issues/208 https://github.com/ruby/openssl/pull/216 The original patch was written by Kazuki Yamaguchi <k@rhe.jp> and the patch for ruby_2_7 branch was prepared by Vít Ondruch.
* bump patchlevel: merge commits: 5c2508060b79b4299a18d05511d3530ad14b1b7a ↵nagachika2020-07-101-2/+2
| | | | 2480ef904c66812cf366e5d9bc8a9c3c20bbf271 47720e2255f34ecad49763c66a7ea02a55a3f60a
* Bison 3.59.1 folds yydestruct function headerNobuyoshi Nakada2020-07-101-0/+1
|
* pure_parser.rb: get rid of an error at localed messagesNobuyoshi Nakada2020-07-101-1/+4
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-26 18:18:36 +0000