| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
test
(https://github.com/ruby/irb/pull/614)
https://github.com/ruby/irb/commit/e68c6128aa
|
|
|
|
|
|
| |
https://github.com/rubygems/rubygems/pull/6766
https://github.com/rubygems/rubygems/commit/c5c5797227
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/68cc941bed
|
|
|
|
|
|
| |
Molinillo::Resolver#resolve
https://github.com/rubygems/rubygems/commit/1c39e24c95
|
|
|
|
| |
https://github.com/ruby/yarp/commit/4deb7c3ae0
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/yarp/commit/52bed3cbe2
|
|
|
|
| |
https://github.com/ruby/yarp/commit/08f08a6cc4
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.1.3 to 2.2.0.
- [Release notes](https://github.com/ossf/scorecard-action/releases)
- [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md)
- [Commits](https://github.com/ossf/scorecard-action/compare/80e868c13c90f172d68d1f4501dee99e2479f7af...08b4669551908b1024bb425080c797723083c031)
---
updated-dependencies:
- dependency-name: ossf/scorecard-action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
|
|
|
| |
https://github.com/ruby/uri/commit/0b6ad60af6
|
|
|
|
|
|
| |
In relative referece, host part can be ommitted but can not be empty.
https://github.com/ruby/uri/commit/2980f0ba02
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
check_code_block(rename to check_code_syntax)
(https://github.com/ruby/irb/pull/611)
https://github.com/ruby/irb/commit/b7f4bfaaa4
|
|
|
|
|
|
|
| |
string
(https://github.com/ruby/irb/pull/610)
https://github.com/ruby/irb/commit/f01ff0811b
|
|
|
|
| |
Fixes [Bug #19569]
|
| |
|
| |
|
|
|
|
| |
Clang 17 does not know warning group '-Wgnu-empty-initializer'.
|
|
|
|
|
|
| |
Full path name of the source directory is a useless noise as tests.
https://github.com/ruby/yarp/commit/44a7ae2e64
|
|
|
|
| |
https://github.com/ruby/yarp/commit/f3fbc5bf9e
|
|
|
|
| |
https://github.com/ruby/yarp/commit/1764532572
|
|
|
|
| |
https://github.com/ruby/yarp/commit/03f5a330a9
|
|
|
|
| |
This is for implementing the `duphash` instruction
|
|
|
|
|
|
|
| |
This test fails on Solaris SPARC with the following error and I can't
figure out why:
TestGCCompact#test_moving_hashes_down_size_pools
Expected 499 to be >= 500.
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/timeout/commit/413194f8d2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/timeout/pull/30)
throw/catch is used for non-local control flow, not for exceptional situations.
For exceptional situations, raise should be used instead. A timeout is an
exceptional situation, so it should use raise, not throw/catch.
Timeout's implementation that uses throw/catch internally causes serious problems.
Consider the following code:
```ruby
def handle_exceptions
yield
rescue Exception => exc
handle_error # e.g. ROLLBACK for databases
raise
ensure
handle_exit unless exc # e.g. COMMIT for databases
end
Timeout.timeout(1) do
handle_exceptions do
do_something
end
end
```
This kind of design ensures that all exceptions are handled as errors, and
ensures that all exits (normal exit, early return, throw/catch) are not
handled as errors. With Timeout's throw/catch implementation, this type of
code does not work, since a timeout triggers the normal exit path.
See https://github.com/rails/rails/pull/29333 for an example of the damage
Timeout's design has caused the Rails ecosystem.
This switches Timeout.timeout to use raise/rescue internally. It adds a
Timeout::ExitException subclass of exception for the internal raise/rescue,
which Timeout.timeout will convert to Timeout::Error for backwards
compatibility. Timeout::Error remains a subclass of RuntimeError.
This is how timeout used to work in Ruby 2.0. It was changed in Ruby 2.1,
after discussion in [Bug #8730] (commit
https://github.com/ruby/timeout/commit/238c003c921e in the timeout repository). I
think the change from using raise/rescue to using throw/catch has caused
significant harm to the Ruby ecosystem at large, and reverting it is
the most sensible choice.
From the translation of [Bug #8730], it appears the issue was that
someone could rescue Exception and not reraise the exception, causing
timeout errors to be swallowed. However, such code is broken anyway.
Using throw/catch causes far worse problems, because then it becomes
impossible to differentiate between normal control flow and exceptional
control flow.
Also related to this is [Bug #11344], which changed how
Thread.handle_interrupt interacted with Timeout.
https://github.com/ruby/timeout/commit/f16545abe6
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
|
| |
SunC warns use of `NULL`, pointer to data as function pointers.
|
|
|
|
|
| |
RHASH_TABLE_NULL_P and ar_alloc_table are no longer needed since
all Hash will have AR tables.
|
|
|
|
|
|
|
| |
(https://github.com/ruby/reline/pull/557)
`get_mbchar_byte_size_by_first_char` isn't used in Reline.
Also, this method implements the same functionality as `String#bytesize` and is unnecessary.
|
|
|
|
|
|
|
|
| |
private
Fixes [Bug #19479]
https://github.com/ruby/ipaddr/commit/7faa0768d3
|
|
|
|
| |
https://github.com/ruby/yarp/commit/89a00203af803032383338c943836da6bafca7d9
|
|
|
|
| |
https://github.com/ruby/yarp/commit/4560cab235
|
|
|
|
| |
https://github.com/ruby/yarp/commit/83c2c45b28
|
|
|
|
| |
https://github.com/ruby/yarp/commit/df6661740c
|
| |
|
| |
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/140405cee6
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/0d10063824
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a7c015f82b
|
| |
|