Age | Commit message (Collapse) | Author |
|
The error message has an integer overflow because it treats an unsigned int as a signed int.
Before:
```
> 3_000_000_000.chr
-1294967296 out of char range (RangeError)
```
After:
```
> 3_000_000_000.chr
3000000000 out of char range (RangeError)
```
Redmine ticket: https://bugs.ruby-lang.org/issues/17186
Notes:
Merged: https://github.com/ruby/ruby/pull/3602
|
|
|
|
Some regexps were too tolerant.
https://github.com/ruby/webrick/commit/8946bb38b4
|
|
|
|
|
|
Try update and extract bundled gems only when baseruby is
available. It should be done only when installing from
developemental build and not from the tarball, but it is not
obvious to differentiate them.
|
|
|
|
http://rubyci.s3.amazonaws.com/ubuntu2004/ruby-master/log/20200929T003003Z.log.html.gz
```
warning: ambiguous first argument; put parentheses or a space even after `/' operator
```
|
|
Reported by Mau Magnaguagno See: https://github.com/ruby/ruby/pull/3570#discussion_r495465903
|
|
|
|
Another ASAN fix. THEAP header is poisoned, so we need to un-poison
before reading
|
|
* Enhanced RDoc for String#succ!
Notes:
Merged-By: BurdetteLamar <BurdetteLamar@Yahoo.com>
|
|
Heap allocated objects are never special constants. Since we're walking
the heap, we know none of these objects can be special. Also, adding
the object to the freelist will poison the object, so we can't check
that the type is T_NONE after poison.
|
|
Invalidating call cache walks the heap, so we need to take care to
un-poison objects when examining them
|
|
I want to work with ASAN, but some child environments are not inheriting
the ASAN options I'm using. This commit passes them to child
environments if specified
|
|
This adds the following C-API functions that can be used to emit
warnings with categories included:
```c
void rb_category_warn(const char *, const char*, ...)
void rb_category_warning(const char*, const char*, ...)
```
Internally in error.c, there is an rb_warn_category function
that will call Warning.warn with the string and the category
keyword if it doesn't have an arity of 1, and will call
Warning.warn with just the string if it has an arity of 1.
This refactors the rb_warn_deprecated{,_to_remove} functions
to use rb_warn_category.
This makes Kernel#warn accept a category keyword and pass it
to Warning.warn, so that Ruby methods can more easily emit
warnings with categories. rb_warn_category makes sure that
the passed category is a already defined category symbol
before calling Warning.warn.
The only currently defined warning category is :deprecated,
since that is what is already used. More categories can be
added in later commits.
Notes:
Merged: https://github.com/ruby/ruby/pull/3508
|
|
In general accepting arbitrary keywords is a bad idea unless you are
delegating keywords or acting on arbitrary keywords. In this case,
the category keyword is ignored, and it's less error prone to not
ignore all keywords.
Notes:
Merged: https://github.com/ruby/ruby/pull/3508
|
|
The documentation already stated this was an error in one case
(when it was previously a warning). Describe the other case,
where chdir without block is called inside block passed to chdir.
Fixes [Bug #15661]
Notes:
Merged: https://github.com/ruby/ruby/pull/3591
|
|
|
|
We have code common to all heap iteration paths in this file. Refactor
such that we keep ASAN checks and flags checks in one place
Notes:
Merged: https://github.com/ruby/ruby/pull/3592
|
|
Again, this code is walking the heap. Empty slots can be poisoned, so
we need to unpoison before checking the type
Notes:
Merged: https://github.com/ruby/ruby/pull/3592
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3592
|
|
ext/objspace iterates over the heap, but some slots in the heap are
poisoned, so we need to take care of that when running with ASAN
Notes:
Merged: https://github.com/ruby/ruby/pull/3592
|
|
|
|
|
|
|
|
|
|
https://github.com/ruby/racc/commit/872f75cfa7
|
|
|
|
|
|
|
|
In an executable script, the shebang line should be the first line (the
file needs to start with the bytes 0x23 0x21). Putting a comment above
it will break the script.
(Regression test included per @deivid-rodriguez)
https://github.com/rubygems/rubygems/commit/962e669feb
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
As splitting by NUL means to allow the file names to contain
newlines, path names should match at beginning-of-string instead
of beginning-of-line.
https://github.com/rubygems/rubygems/commit/8a81183236
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
Sometimes "install_dir/cache" directory is not writable although "install_dir" is writable.
https://github.com/rubygems/rubygems/commit/665221cb69
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
As far as I could see, `Gem::Resolver::APISpecification` objects are
supposed to be immutable. If my guessing is correct, then we can cache
and reuse its instances for performance.
At least, `rake` passes on my machine.
Before this change:
```
$ time ruby -I lib bin/gem install --no-doc aws-sdk
Successfully installed aws-sdk-3.0.1
1 gem installed
real 0m37.104s
user 0m36.952s
sys 0m0.333s
```
After this change:
```
$ time ruby -I lib bin/gem install --no-doc aws-sdk
Successfully installed aws-sdk-3.0.1
1 gem installed
real 0m23.905s
user 0m23.740s
sys 0m0.365s
```
https://github.com/rubygems/rubygems/commit/7e8fbba85c
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/d498ae3d62
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
--system --silent`
https://github.com/rubygems/rubygems/commit/038203aaf8
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/c3fb0db930
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/5a1e56e892
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/dd87d70f51
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
Consider the version original included with each ruby as the minimum
supported version.
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
help message
https://github.com/rubygems/rubygems/commit/38230a77c1
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/087a1f9720
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/1715610648
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/addc644cad
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
Its `__has_declspec_attribute()` is not reliable. For instance,
while `__has_declspec_attribute(noalias)` is true but 'noalias'
attribute is warned as unknown.
|
|
|
|
|
|
|