| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://github.com/rubygems/rubygems/commit/75f672ff0e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When installing in parallel, bundler creates several `Gem::Installer`
instances that run in parallel. These installers access the `@@all` class
variable of `Gem::Specification` concurrently.
If a concurrent thread calls `Gem::Specification.reset` (resetting
`@all` to `nil`) while another thread is running
`Gem::Specification._all` or another method that expects `@@all` to be
loaded and not `nil`, that can result in `Enumerable` methods being
called on `nil`, resulting in crashes.
I fix it by protecting the other concurrent access to the `@all`
variable.
https://github.com/rubygems/rubygems/commit/58b343c530
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/e9e25731d8
|
|
|
|
|
| |
I'm trying to find why a reference to an IMEMO object isn't being
updated
|
| |
|
|
|
|
|
|
| |
We have `__dir__` which is the same thing.
https://github.com/rubygems/rubygems/commit/f89776427f
|
|
|
|
|
|
|
|
|
| |
I don't know why it was living at the class level. At first I thought it
would be to reuse some server instances between tests, but they seem to
be cleaned up after every test anyways, so I don't think any of it is
needed.
https://github.com/rubygems/rubygems/commit/04bee71216
|
| |
|
| |
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a0219b9f27
|
|
|
|
|
|
|
| |
* One should not compare RUBY_ENGINE and Gem::Platform.
* Introduced in https://github.com/rubygems/rubygems/pull/2672
https://github.com/rubygems/rubygems/commit/0e62c3be91
|
|
|
|
|
|
| |
* Other Ruby implementations don't support $SAFE.
https://github.com/rubygems/rubygems/commit/9a4ba16efa
|
|
|
|
|
|
|
|
| |
- Resolver asked Molinillo to resolve-then-activate, which led to using Gem::NameTuple before any require had been passed
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
https://github.com/rubygems/rubygems/commit/e11782b0c8
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1a72c8796f
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c07b9cf4f1
|
|
|
|
|
|
| |
move rubyforge_project= to removed methods
https://github.com/rubygems/rubygems/commit/223f7fd470
|
|
|
|
|
|
| |
time.
https://github.com/rubygems/rubygems/commit/c44eb21648
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/965eee1741
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/024267fa60
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6afd914fda
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/984bb9b815
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/db5bb65baf
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4fe5bb5bf3
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/b679ab27af
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/3a14635cf5
|
|
|
|
|
|
| |
version instead of a date
https://github.com/rubygems/rubygems/commit/bf95b1de78
|
|
|
|
|
|
| |
instead of a date
https://github.com/rubygems/rubygems/commit/f0e098a1b7
|
| |
|
|
|
|
|
|
|
|
| |
It was migrated on ruby core repository too.
https://github.com/ruby/ruby/commit/e5db3da9d34f0a7595208863301c044b612adbed
https://github.com/rubygems/rubygems/commit/848bbe3c76
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/afa01a29a3
|
|
|
|
|
|
| |
These changes completely broke the test suite on ruby core repository.
https://github.com/rubygems/rubygems/commit/84b0bea3e1
|
|
|
|
|
|
|
|
|
| |
Our tests are now guaranteed to not work on older versions of minitest,
so I don't think we should swallow this activation error because it will
make it very clear for the user what the problem is if she has a
minitest version not satisfying the requirement.
https://github.com/rubygems/rubygems/commit/a291b65369
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/aec3887d9c
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/24213b97d8
|
|
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f2cc5d7033
https://github.com/rubygems/rubygems/commit/ae5b4e2043
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/2890622479
|
| |
|
|
|
|
| |
This just introduces compaction support for backtrace objects.
|
|
|
|
|
|
|
|
|
|
| |
This patch allows global variables that have been assigned in Ruby to
move. I added a new function for the GC to call that will update
global references and introduced a new callback in the global variable
struct for updating references.
Only pure Ruby global variables are supported right now, other
references will be pinned.
|
| |
|
|
|
|
|
|
| |
Right now `SomeClass.method` is properly named, but `SomeModule.method`
is displayed as `#<Module:0x000055eb5d95adc8>.method` which makes
profiling annoying.
|
|
|
|
|
|
|
| |
No objects should ever reference a `T_MOVED` slot. If they do, it's
absolutely a bug. If we kill the process when `T_MOVED` is pushed on
the mark stack it will make it easier to identify which object holds a
reference that hasn't been updated.
|
|
|
|
| |
IRB::ReadlineInputMethod#initialize changes them via IRB.set_encoding.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It caches a path to .irbrc file, which has caused random failure:
```
1) Failure:
TestIRB::ExtendCommand#test_irb_info_multiline [/home/mame/work/ruby/test/irb/test_cmd.rb:49]:
Expected /
Ruby\sversion: .+\n
IRB\sversion:\sirb .+\n
InputMethod:\sReidlineInputMethod\swith\sReline .+ and .+\n
\.irbrc\spath: .+
/x to match "Ruby version: 2.8.0\n" +
"IRB version: irb 1.2.3 (2020-02-15)\n" +
"InputMethod: ReidlineInputMethod with Reline 0.1.4 and /tmp/test_reline_config_155659/.inputrc\n".
```
|
| |
|
| |
|
|
|
|
| |
There is parse.h apart from parse.c these days.
|
|
|
|
| |
This file is not under Ruby's license.
|
|
|
|
|
| |
IBM holds their copyrights. Whether they are free software or not is
uncler. But arguably they are, given we have copied them from glibc.
|
|
|
|
| |
The file was moved.
|