aboutsummaryrefslogtreecommitdiffstats
path: root/version.h
Commit message (Collapse)AuthorAgeFilesLines
* merge revision(s) 927308108cced69cae478798004524b9a5d2f252: [Backport #16764]nagachika2020-07-231-1/+1
| | | | Fix source location of autoloaded constant [Bug #16764]
* merge revision(s) da05c1552ee519d8f180b48d97148d28501acb35: [Backport #16749]nagachika2020-07-231-1/+1
| | | | Update to ruby/spec@cc7b9e5
* merge revision(s) 72c02aa4b79731c7f25c9267f74b347f1946c704: [Backport #16662]nagachika2020-07-231-1/+1
| | | | | | | 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-231-1/+1
| | | | | | | | | | | | | | | 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]
* merge revision(s) e04418bb16cd99b4a4402e7457d3bdc967284f98: [Backport #16830]nagachika2020-07-231-1/+1
| | | | | | | | [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-231-1/+1
| | | | | | Fix ObjectSpace::WeakMap#key? to work if the value is nil * Fixes [Bug #16826]
* merge revision(s) 579645d9f870fa4116dcd3200bbbb6e2c0b7f400: [Backport #17033]nagachika2020-07-231-1/+1
| | | | Fixed infinite loop at error in printing cause [Bug #17033]
* merge revision(s) 99a9c3fe2eaab8157765d792dc871da6daea0327: [Backport #17024]nagachika2020-07-231-1/+1
| | | | Fixed yday and wday with timezone [Bug #17024]
* merge revision(s) 2ecfb88ee50510955acd3ae9fc94a5f109e7f109: [Backport #16918]nagachika2020-07-231-1/+1
| | | | | | | | | 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-231-2/+2
| | | | | | | | | | 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-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-191-1/+1
| | | | | | | | | 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-191-1/+1
| | | | | | | | | | | | | | | | 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-191-2/+2
| | | | | | | | | | 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
|
* OpenSSL 1.1.1 introduces a new '.include' directive. Update our confignagachika2020-07-111-2/+2
| | | | | | | | | | | | | | | | 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
* merge revision(s) ↵nagachika2020-07-091-1/+1
| | | | | | | | 87ad5ea729735ff6b8f1ac0bb3aad2aedd6f716e,9745e90197f129708986803e8913fb151862478a: Skip jit_test on some new RubyCI envs for now Propagate JIT skip to all tests
* merge revision(s) 21d8e6924844d592ff2d5a2e7309457eb92e66f6:nagachika2020-07-091-2/+2
| | | | | | | | disable to show the maximum number of threads. On Deiban 9 environment, the thread tests failed and this maximum threads information can finish up the machine resources. To check it, I turned-off showing this information.
* merge revision(s) 75802bcff1b941818832f0145071f7ce9c843d8d:nagachika2020-07-051-3/+3
| | | | | | | | | | | | | configure: suppress icc warnings Every time a pointer to/from VALUE conversion happens, these two warnings are issued: - warning #1684: conversion from pointer to same-sized integral type (potential portability problem) - warning #2312: pointer cast involving 64-bit pointed-to type Thank you, but we are well aware of the "potential portability problem". Let us ignore them all.
* merge revision(s) a19228f878d955eaf2cce086bcf53f46fdf894b9: [Backport #16979]nagachika2020-06-271-1/+1
| | | | | | | | | brace the fact that lchmod(2) can EOPNOTSUPP Musl libc has this function as a tiny wrapper of fchmodat(3posix). On the other hand Linux kernel does not support changing modes of a symlink. The operation always fails with EOPNOTSUPP. This fchmodat behaviour is defined in POSIX. We have to take care of such exceptions.
* merge revision(s) 263b941321c3de6afc8f9dafbc2625f866b7437e: [Backport #16981]nagachika2020-06-271-2/+2
| | | | | | | [ripper] fix mismatched indentations warning [Bug #16981] The scanner location has to be set from `lex.ptok` before it is flushed by dispatching the scanner event.
* merge revision(s) 7e289cdf3fed588b2d5a6973e29f9ff95cb8d76c: [Backport #16949]nagachika2020-06-131-2/+2
| | | | | | | | | | | [ruby/psych] Fixing compatibility with libyaml 0.2.5 The main issue is that commas aren't allowed in local tags. libyaml was updated to follow the spec, and our tests were out of date. See: https://github.com/yaml/libyaml/issues/196 https://github.com/ruby/psych/commit/3f5e520fd3
* * 2020-06-08 [ci skip]git2020-06-081-1/+1
|
* merge revision(s) ↵nagachika2020-06-071-3/+3
| | | | | | | | ac2106acc276854ae2ac8cc5fa6859aa28362f2f,cf90df22c74da2f87421749e8d065cfbd3812afd: [Backport #16813] [DOC] Fixed explanation for Method#>> [Bug #16813] [ci skip] [DOC] Separated Method#[] from Method#call [Bug #16813] [ci skip]
* v2.7.1p83v2_7_1NARUSE, Yui2020-03-311-1/+1
|
* * 2020-03-31 [ci skip]git2020-03-311-1/+1
|
* * 2020-03-30 [ci skip]git2020-03-301-1/+1
|
* * 2020-03-28 [ci skip]git2020-03-281-1/+1
|
* * 2020-03-26 [ci skip]git2020-03-261-1/+1
|
* * 2020-03-15 [ci skip]git2020-03-151-1/+1
|
* * 2020-03-14 [ci skip]git2020-03-141-1/+1
|
* * 2020-03-13 [ci skip]git2020-03-131-2/+2
|
* * 2020-02-20 [ci skip]git2020-02-201-1/+1
|
* * 2020-02-18 [ci skip]git2020-02-181-1/+1
|
* increment teenyNARUSE, Yui2020-02-181-2/+2
|
* * 2020-02-13 [ci skip]git2020-02-131-3/+3
|
* v2.7.0p0NARUSE, Yui2019-12-251-1/+1
|
* * 2019-12-25 [ci skip]git2019-12-251-1/+1
|
* * 2019-12-24 [ci skip]git2019-12-241-1/+1
|
* * 2019-12-23 [ci skip]git2019-12-231-1/+1
|
* * 2019-12-22 [ci skip]git2019-12-221-1/+1
|
* * 2019-12-21 [ci skip]git2019-12-211-1/+1
|
* * 2019-12-20 [ci skip]git2019-12-201-1/+1
|
* * 2019-12-19 [ci skip]git2019-12-191-1/+1
|
* * 2019-12-18 [ci skip]v2_7_0_rc1git2019-12-181-1/+1
|
* * 2019-12-17 [ci skip]git2019-12-171-1/+1
|
* * 2019-12-16 [ci skip]git2019-12-161-1/+1
|
* * 2019-12-15 [ci skip]git2019-12-151-1/+1
|
* * 2019-12-14 [ci skip]git2019-12-141-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-10 15:32:09 +0000