summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Skip tainted examples for stringioHiroshi SHIBATA2019-10-313-14/+22
|
* [ruby/stringio] Remove taint supportJeremy Evans2019-10-312-15/+0
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/stringio/commit/60ee9ccd95
* [ruby/date] Revert "Simplify #inspect"Jeremy Evans2019-10-312-4/+5
| | | | | | | | This reverts commit af01edd7d8575f544f647dbe8cde5b6ae535d459. Revert requested by Yui Naruse. https://github.com/ruby/date/commit/875d563557
* [ruby/date] introduce Date::Error, raise Date::Error for everyglaszig2019-10-314-57/+71
| | | | | | "invalid <anything>" type of exception https://github.com/ruby/date/commit/3e55c09ba4
* [ruby/fileutils] Remove use of untaint on Ruby 2.7 to avoid deprecation warningsJeremy Evans2019-10-311-1/+2
| | | | https://github.com/ruby/fileutils/commit/5ac9a8a1f7
* [ruby/gdbm] Use Gemfile instead of ↵Hiroshi SHIBATA2019-10-311-5/+0
| | | | | | Gem::Specification#add_development_dependency. https://github.com/ruby/gdbm/commit/bd2e7f6647
* [ruby/gdbm] Remove taint supportJeremy Evans2019-10-311-3/+0
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/gdbm/commit/f9aaa1a08d
* [ruby/zlib] Remove taint supportJeremy Evans2019-10-312-36/+1
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/zlib/commit/21711ed0ce
* Mention update to Unicode Emoji version 12.1 in NEWS.Martin Dürst2019-10-311-1/+3
| | | | Also fixed some grammatical errors. [ci skip]
* Fixed the sync task for jsonHiroshi SHIBATA2019-10-311-3/+2
| | | | | * Ignode to change ext/json/depend * Fixed to ignore json_pure files
* Revert "Fix zero free objects assertion"Aaron Patterson2019-10-301-29/+15
| | | | | | This reverts commit e1bf29314feee6aaf535917da0178e868e7ff3fa. I'm not sure why this broke stuff, I need to investigate later.
* Fix zero free objects assertionAaron Patterson2019-10-301-15/+29
| | | | | | | | | | | | | | | | | This commit is to attempt fixing this error: http://ci.rvm.jp/results/trunk-gc-asserts@ruby-sky1/2353281 Each non-full heap_page struct contains a reference to the next page that contains free slots. Compaction could fill any page, including pages that happen to be linked to as "pages which contain free slots". To fix this, we'll iterate each page, and rebuild the "free page list" depending on the number of actual free slots on that page. If there are no free slots on the page, we'll set the free_next pointer to NULL. Finally we'll pop one page off the "free page list" and set it as the "using page" for the next allocation.
* Also ignore mswin platformHiroshi SHIBATA2019-10-311-1/+1
|
* Ignore test_racc_command with linux platformHiroshi SHIBATA2019-10-311-1/+1
|
* Try to run assert_output_unchanged with racc testsHiroshi SHIBATA2019-10-313-25/+38
|
* * 2019-10-31 [ci skip]git2019-10-311-1/+1
|
* Allow only one argument for keyword_init structAlan Wu2019-10-312-1/+2
| | | | | | | | | | | | | | | ``` irb(main):001:0> RUBY_VERSION => "2.6.5" irb(main):002:0> S = Struct.new(:foo, keyword_init: true) => S(keyword_init: true) irb(main):003:0> S.new({foo: 23424}, 234) # I don't think this is intentional => #<struct S foo=23424> irb(main):004:0> ``` Tightening this up should inform users when they are confused about whether a struct is `keyword_init`.
* Update the latest versions from upstream repository of raccHiroshi SHIBATA2019-10-3010-18/+21
|
* Regenerate the output results for test fixtures of raccHiroshi SHIBATA2019-10-3029-2556/+2556
|
* Update the latest structure for racc upstreamHiroshi SHIBATA2019-10-301-1/+3
|
* Update Unicode Emoji version from 12.0 to 12.1.Martin Dürst2019-10-301-1/+1
| | | | | | | | | | This update does not add any new codepoint assignments, it just expands the range of emoji codepoint sequences recommended for public interchange. Depending on how emoji data files are cached, this commit may require manual intervention in some build environments (including some CI systems).
* * 2019-10-30 [ci skip]git2019-10-301-1/+1
|
* Compacting the heap can cause GC, so disable itAaron Patterson2019-10-291-1/+1
| | | | | | | When we compact the heap, various st tables are updated, particularly the table that contains the object id map. Updating an st table can cause a GC to occur, and we need to prevent any GC from happening while moving or updating references.
* Fix tests for CVE-2018-6914Nobuyoshi Nakada2019-10-293-72/+64
| | | | | | | | | Since the current working directory is not involved in `Tempfile` and `Dir.mktmpdir` (except for the last resort), it is incorrect to derive the traversal path from it. Also, since the rubyspec temporary directory is created under the build directory, this is not involved in the target method. Fixed sporadic errors in test-spec.
* Check for nonnull attribute in configureNobuyoshi Nakada2019-10-293-4/+12
|
* Revert "Check for nonnull attribute in configure"卜部昌平2019-10-292-9/+4
| | | | | | This reverts commit 54eb51d72bc43f90b595f0d7ffb5069ebf1a56d9. Windows build failure. See also https://github.com/ruby/ruby/runs/278718805
* test/rubygems/test_gem.rb: early failure when there is /tmp/GemfileYusuke Endoh2019-10-291-0/+4
| | | | | | | | | | | | | | | Some test cases in rubygems assume that /tmp/Gemfile does not exist. If it does, they fail with very difficult-to-understand message: ``` [ 149/2108] TestGemBundlerVersionFinder#test_bundler_version_with_bundle_update_bundler = 0.00 1) Failure: TestGemBundlerVersionFinder#test_bundler_version_with_bundle_update_bundler [/home/mame/work/ruby/test/rubygems/test_gem_bundler_version_finder.rb:38]: Expected Gem::Version.new("2.0.2") to be nil. ``` I spent one hour to debug this issue. To prevent the same accident, this change makes the test suite stop when /tmp/Gemfile explicitly.
* Revert "Revert "[ruby/rdoc] Use omit of test-unit instead of skip of minitest""Yusuke Endoh2019-10-297-13/+13
| | | | | | This reverts commit ca5812fe4516a10cc687281f9e47e1a08449f1ab. Now tool/lib/minitest provides "omit", so it should work.
* tool/lib/minitest/unit.rb: add "omit" as an alias to "skip"Yusuke Endoh2019-10-291-0/+2
| | | | | | According to rdoc, test-unit provides omit instead of skip. This is a compatibility layer to make it work with both test-unit and tool/lib/minitest.
* Revert "[ruby/rdoc] Use omit of test-unit instead of skip of minitest"Yusuke Endoh2019-10-297-13/+13
| | | | | | This reverts commit b4da6fc1c277190bbd10e795ebf3be45772038e8. `make test-all` uses minitest, which led to "undefined method `omit'"
* [ruby/rdoc] Use Dir.glob to convert short path of Dir.tmpdir to long pathaycabta2019-10-291-0/+8
| | | | https://github.com/ruby/rdoc/commit/ba16e44572
* [ruby/rdoc] Support different drive latters in include pathsaycabta2019-10-292-5/+26
| | | | https://github.com/ruby/rdoc/commit/946d2592e2
* [ruby/rdoc] Use omit of test-unit instead of skip of minitestaycabta2019-10-297-13/+13
| | | | https://github.com/ruby/rdoc/commit/1c5bf2ae1d
* Check for nonnull attribute in configureNobuyoshi Nakada2019-10-292-4/+9
|
* Clang can also use C call cacheJohn Hawthorn2019-10-291-1/+1
| | | | | | | | Previously this was restricted to only gcc because of the GCC_VERSION_SINCE check (which explicitly excludes clang). GCC 3.3.0 is quite old so I feel relatively safe assuming that all reasonable versions of clang support this.
* Let the arrays for the singleton and instance method reflection helpers be ↵Lourens Naudé2019-10-291-2/+2
| | | | initialized to the methods count
* Let the backtrace array constructed in backtrace_collect be initialized with ↵Lourens Naudé2019-10-291-1/+1
| | | | the size already given
* Right size the vm_default_params hashLourens Naudé2019-10-291-1/+1
|
* Right size the Enumerator internal lazy_use_super_method hashLourens Naudé2019-10-291-1/+1
|
* Right size the compile option hashLourens Naudé2019-10-291-1/+1
|
* Right size the iseq coverage branches tmp array - initializes with 5 elementsLourens Naudé2019-10-291-1/+1
|
* Version 0.0.4aycabta2019-10-291-1/+1
|
* Restore `in_kwarg` flag properlyNobuyoshi Nakada2019-10-292-1/+2
|
* Revert "Protect finalizer references during execution"Aaron Patterson2019-10-281-12/+15
| | | | | | | | This reverts commit 60a7f9f446604571f8a81499080c57c47baf0e6b. We can't have Ruby objects pointing at T_ZOMBIE objects otherwise we get an error in the GC. We need to find a different way to update references.
* Protect finalizer references during executionAaron Patterson2019-10-281-15/+12
| | | | | | | | | | | | | | | | When we run finalizers we have to copy all of the finalizers to a new data structure because a finalizer could add another finalizer and we need to keep draining the "real" finalizer table until it's empty. We don't want Ruby programs to mutate the finalizers that we're iterating over as well. Before this commit we would copy the finalizers in to a linked list. The problem with this approach is that if compaction happens, the linked list will need to be updated. But the GC doesn't know about the existence of the linked list, so it could not update references. This commit changes the linked list to be a Ruby array so that when compaction happens, the arrays will automatically be updated and all references remain valid.
* Fix continuation mark / compactAaron Patterson2019-10-281-0/+6
|
* Pin labels during disassemblyAaron Patterson2019-10-281-4/+20
| | | | | | | We need to ensure that labels are pinned while disassembling. If the compactor runs during disassembly, references to these labels could go bad, so this commit just ensures that the labels can't move until we're done.
* Pin keys of this st_tableAaron Patterson2019-10-281-1/+1
|
* * 2019-10-29 [ci skip]git2019-10-291-1/+1
|
* Marshal is calling functions that should pin thingsAaron Patterson2019-10-281-2/+12
|
View Lorry Controller Status