| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
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.
Still untaint the tmpdir object on Ruby <2.7, as returning
a tainted string there could cause problems.
|
|
|
|
| |
Ruby 2.7 deprecates taint and it no longer has an effect.
|
|
|
|
| |
Ruby 2.7 deprecates taint and it no longer has an effect.
|
| |
|
|
|
|
|
|
| |
This removes the related tests, and puts the related specs behind
version guards. This affects all code in lib, including some
libraries that may want to support older versions of Ruby.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the security features added by $SAFE = 1, and warns for access
or modification of $SAFE from Ruby-level, as well as warning when calling
all public C functions related to $SAFE.
This modifies some internal functions that took a safe level argument
to no longer take the argument.
rb_require_safe now warns, rb_require_string has been added as a
version that takes a VALUE and does not warn.
One public C function that still takes a safe level argument and that
this doesn't warn for is rb_eval_cmd. We may want to consider
adding an alternative method that does not take a safe level argument,
and warn for rb_eval_cmd.
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/irb/commit/0180dc74bc
|
|
|
|
| |
https://github.com/ruby/irb/commit/4945d0e676
|
|
|
|
| |
https://github.com/ruby/reline/commit/d57c7ea252
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/reline/commit/98b72af751
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The script in prelude.rb was embed in MRI to load it (eval this
script at everyboot).
This commit change the loading process of prelude.rb. MRI doesn't
eval a script, but load from compiled binary with builtin feature.
So that Init_prelude() does not load `prelude.rb` now.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Looking at the list of symbols inside of libruby-static.a, I found
hundreds of functions that are defined, but used from nowhere.
There can be reasons for each of them (e.g. some functions are
specific to some platform, some are useful when debugging, etc).
However it seems the functions deleted here exist for no reason.
This changeset reduces the size of ruby binary from 26,671,456
bytes to 26,592,864 bytes on my machine.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
rb_vm_lvar_exposed() is prepared for __builtin_inline!(), needed for
mini_builtin.c and builtin.c. However, it's only on builtin.c.
So move it to make it as a part of VM.
|
|
|
|
|
|
|
|
| |
https://github.com/ruby/ruby/runs/301411717
No C backtrace information and this is hard to fix immediately.
As CI doesn't provide helpful information, this should be debugged
locally or at least have more logs there.
|
|
|
|
|
| |
Build's sequential number is a link in Travis, and also YYYY-MM-DD-XX is
a little hard to parse.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
commit number of today requires log since 0:00 UTC.
So commits of 24 hours are enough.
https://www.git-scm.com/docs/git-clone#Documentation/git-clone.txt---depthltdepthgt
> Implies --single-branch unless --no-single-branch is given to fetch the histories near the tips of all branches.
So I add `--single-branch` too.
|
| |
|
| |
|
|
|
|
| |
failing in https://github.com/ruby/ruby/runs/300579218
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes [Bug #16332]
Constant access was changed to no longer allow top-level constant access
through `nil`, but `defined?` wasn't changed at the same time to stay
consistent.
Use a separate defined type to distinguish between a constant
referenced from the current lexical scope and one referenced from
another namespace.
|
|
|
|
| |
Co-authored-by: Kazuhiro NISHIYAMA <zn@mbf.nifty.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Migrate Wercker MJIT tests to Actions
* Support pull request for testing
* Capitalize other jobs too
* Make it a command name for consistency [ci skip]
* Remove wercker.yml
* Add --jit-verbose=2 for debugging
* Install MJIT headers
* Separate install for sudo
* Trigger build
|
| |
|
|
|
|
| |
See L25-28
|
|
|
|
| |
At least the comment looks obsoleted. Aren't we using $JOBS already?
|
|
|
|
|
|
| |
Hoping to make it like `make (check, ...)`, `make (test-bundler, ...)`
instead of `latest (...)` because some of the jobs are already not
running on a latest platform.
|
|
|
|
| |
only once. Doing it on multiple Ubuntu versions may not worth it.
|
| |
|
|
|
|
| |
https://help.github.com/en/actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions#set-an-environment-variable-set-env
|
| |
|