Activity
From 10/16/2023 to 10/22/2023
10/22/2023
-
08:17 PM Revision 11468269 (git): [rubygems/rubygems] Fix spelling of extraneous
- https://github.com/rubygems/rubygems/commit/af61829432
-
04:03 PM Feature #19744: Namespace on read
- Let me clarify the example using `X`, because the integer value and the wording may confuse, perhaps.
If `foo.rb` has
```ruby
X = 1
```
I expect as a Ruby programmer that in the next line `Object.constants` includes `:X`. If c... -
- @Eregon I understand the patch is a partial implementation of the proposal (also, the author of the ticket said `Object` and `ns::Object` would be different).
It cannot be otherwise, because if `Object` and `ns::Object` where the same o... -
11:12 AM Revision b84e6fe9 (git): [DOC] Mention the omission of a superclass when reopening a class
- 09:47 AM Revision e721a7ae (git): [DOC] Update documentation for typical implementation of hash
-
03:18 AM Revision 7578bc35 (git): [ruby/io-console] Intersperse Win32 and termios implementations
- So that the both sources appear in RDoc generated HTMLs.
https://github.com/ruby/io-console/commit/beec164a47 - 02:31 AM Revision 0f02a86a (git): Update default gems list at 8c0c7be65b21dc34156919b04b834e [ci skip]
-
- https://github.com/ruby/io-console/commit/06307a755d
-
- https://github.com/ruby/io-console/commit/13e0bcac9f
10/21/2023
-
-
-
-
- https://github.com/ruby/io-console/commit/62a677b51a
-
- https://github.com/rubygems/rubygems/commit/49aaa46708
-
06:06 PM Revision 745879b5 (git): [ruby/irb] Minor refactors around irb.rb
- (https://github.com/ruby/irb/pull/736)
* Remove dead method
* Simplify IRB.version
* Move private Irb methods together
* Centralise @CONF initialization/assignment in init.rb
* Move attr_* calls above initialize method
https://gith... -
- Applied in changeset commit:git|665b4c5b2a31078d7db0173ad60daad0b463c1fd.
----------
[Bug #19967] Reset `LIBPATHENV` env after started
Not to affect other tools invoked as child processes. -
-
-
-
-
- This reverts commit 1961c786aab243b3eb60e7238224e87975d88056. These
environment variables should no longer propagate to child processes. -
- Not to affect other tools invoked as child processes.
-
-
04:30 AM Revision 55d95472 (git): Raise TypeError for bad IO::Buffer.map argument (#8728)
- * Raise TypeError when IO::Buffer.map argument is neither IO nor implements #fileno
* Use UNREACHABLE_CODE
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
* Use macro for undef check
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-... -
- String locking with locktmp is not really part of the public API,
and the test relies in a side effect of using it to protect the
buffer. On other implementations without locktmp this does not
fail. Separate into its own test so it can b...
10/20/2023
-
08:20 PM Bug #19921 (Closed): TestYJIT#test_bug_19316 test failure
- Thanks! The new message confirms the issue. The test should pass now, as of commit:fab70183.
-
02:12 AM Bug #19921: TestYJIT#test_bug_19316 test failure
- With commit:985370406d2c5150fa3e0f23cdae605ec1a60fdb
```
93) Failure:
TestYJIT#test_bug_19316 [/builddir/build/BUILD/ruby-3.3.0-985370406d/test/ruby/test_yjit.rb:1163]:
Expected no exits, but got:
{:opt_and=>1}
Reasons:
method ... -
08:12 PM Revision 8a88172f (git): YJIT: Skip printing stats at exit if --yjit-disable (#8727)
-
07:29 PM Revision 01787d53 (git): [PRISM] Setup encodings in prism compiler
-
05:38 PM Feature #19744: Namespace on read
- > Yes, Object.object_id != ns1::Object.object_id
OK. I did not expect that and the PoC does not do anything like that.
What about `class C; end` when loaded in a namespace, from which Object does it inherit then?
What about instance... -
03:57 PM Feature #19744: Namespace on read
- If `Object.object_id != ns1::Object.object_id`, I assume `BasicObject.object_id != ns1::BasicObject.object_id`, but Ruby currently does not allow for copying the root class:
```
ruby -e BasicObject.dup
-e:1:in `initialize_copy': can... -
- @tagomoris got it, thanks!
So, if I have
```ruby
class C
end
```
and client code loads that file under a namespace `ns`, then `ns::Object.constants` includes `:C`?
And `::C` in my required code is locally resolved to `Object::C`, whi... -
- > If so, yes. It's planned (and it's working on my PoC branch, without the "Gem Namespaces" feature).
Nice. Thanks for taking the time to answer and clarify.
Also, I think that "gem namespaces" are something that are enabled implic... -
01:51 AM Feature #19744: Namespace on read
- Dan0042 (Daniel DeLorme) wrote in #note-41:
> Would it be possible to use this features to load a Ractor-incompatible library inside a NameSpace inside a Ractor? Let's say:
> ...
@Dan0042 Currently, in this proposal, it's impossible. N... -
- fxn (Xavier Noria) wrote in #note-38:
> What happens with the top-level constants defined by the interpreter? In particular, is `Object.object_id != ns1::Object.object_id != ns2::Object.object_id`?
@fxn This proposal says: "a new fea... -
- martinemde (Martin Emde) wrote in #note-37:
> ### Patching/plugins
> ...
@martinemde Let me check my understanding of your question: "Does Rack (or ::Rack) work with Oj loaded separately in the namespace for `MyGem` after the `include`... -
- Because the `&` call checks for interrupts, the test was accidentally
timing dependent. Stop checking for exits.
[Bug #19921]
Reported-by: Vít Ondruch <vondruch@redhat.com>
Reported-by: Mamoru Tasaka <mtasaka@fedoraproject.org> -
-
-
-
- On macOS, in the case of `--enable-shared` and `--disable-load-relative`, already install libruby.dylib is used during tests if exists.
This is because since [Bug #14992], `DYLD_FALLBACK_LIBRARY_PATH` is used instead of `DYLD_LIBRARY_PA... -
09:26 AM Revision 8b3d0440 (git): [DOC] Indentation fix in comments of MatchData#inspect
- The old version did not add syntax highlighting to the code block, and
included the "Related:" line in the code block as well. -
-
- Applied in changeset commit:git|9d1940ba3c3bd08a8f2c630e51524186e350fdd5.
----------
[Bug #19966] [PRISM] Fix singleton method definition -
- https://github.com/ruby/ruby/pull/8718
-
- The receiver is ignored and compiled to `definemethod` instead of `definesmethod`.
```
$ ./ruby -v -e 'puts RubyVM::InstructionSequence.compile_prism("def a.foo;end").disasm'
ruby 3.3.0dev (2023-10-20T00:12:09Z master 985370406d) [a... -
-
-
05:34 AM Revision bb849ffd (git): Added explicitly begin-end block for Ruby 2.4.
- strscan, ipaddr and some default gems still support Ruby 2.4.
After this, I extract this CoreAssertions to their repositories. -
03:56 AM Revision 9ea1ee66 (git): Stop creating ripper.h because it's not used
-
- https://github.com/ruby/logger/commit/ac911eae2b
-
- https://github.com/ruby/logger/commit/7b51af263f
-
- Having this variable actually helps the performance of non-JITed calls.
----- ----------- ---------- ---------- ---------- ------------- ------------
bench before (ms) stddev (%) after (ms) stddev (%) after 1st itr before/af... -
-
-
- To fix https://github.com/ruby/ruby/actions/runs/6581593578/job/17881779994
-
- Contrary to my initial assumption, rb_threadptr_root_fiber_setup() is
called for each Ractor, not just once at boot. I changed the place to
call rb_jit_cont_init() to avoid calling it multiple times.
10/19/2023
-
11:45 PM Revision 72f97ee0 (git): [DOC] Improve docs for how to generate documentation
- It might not be obvious how to get the build directory and the Makefile
set up. -
- I think it meant it's now a bundled "gem", but "is now bundled" implies
it's a new gem that was neither default nor bundled gems. So I changed
wording.
I also want to change the subjects and reorder them so that it will read:
"The follo... -
- generated by check_misc
-
-
- in tool/update-NEWS-gemlist.rb
-
-
- ARGSCAT has been used for nd_args to hold index and rvalue,
because there was limitation on the number of members for Node.
We can easily change structure of node now, let's expand it. -
-
- --yjit-disable, and --yjit-perf
-
- of => if
-
-
09:40 PM Revision 205cbc09 (git): [rubygems/rubygems] Reuse Gem::RemoteFetcher instance in bundler
- Closes https://github.com/rubygems/rubygems/issues/7076
Bundler will now use the same (shared) remote fetcher instance that
RubyGems uses.
This will allow installs to use a shared connection pool, which
represents a significant perform... -
- Could someone kick off a Koji build with commit:9047fe5ea4e8c989c1081aa10f741a413c546534
"YJIT: Print exit reasons on failure in test_yjit.rb"?
It adds some extra information to the failure message that should resolve this
mystery. This ... -
- See https://github.com/rails/thor/releases/tag/v1.3.0
https://github.com/rubygems/rubygems/commit/3c7165474b -
07:29 PM Revision 3e65115c (git): YJIT: remove unused `--yjit-greedy-versioning` command-line option (#8713)
-
- The for-human stats summaries are not relevant for the children
`test_yjit.rb` spawns. Avoid compiling and running the printing code.
On a -O0 dev build this halves the time for `test_yjit.rb` on my machine. -
- For <https://bugs.ruby-lang.org/issues/19921>, I suspect the test is
failing due to a timing related interrupt, which on paper could
happen with slow-enough GC runs.
In any case, it's helpful for debugging to have more information when
... -
- So that we get a reminder to check CodeBlock::has_dropped_bytes().
Internally, asm.compile() already checks it, and this patch just
propagates it out to the caller with a `#[must_use]`.
Code GC logic moved out one level in entry_stub_hi... -
-
03:57 PM Revision 62e34025 (git): Don't add anonymous locals when ISEQ binary debug is on
-
-
-
- > b) use the perf map file as a source of symbols.
So this is a post I found with quick googling: https://stackoverflow.com/questions/42739893/force-gdb-to-use-frame-pointer-based-unwinding
They say you can at least define a routin... -
- > One question - the perf map file is going to grow without bound for a long-running process, right? I guess there's no real way around this based on how the file is specified though... I'll have a look at that problem when I actually ru...
-
- https://github.com/ruby/ostruct/commit/ed49920766
-
- * [Feature #18980] Re-reconsider numbered parameters: `it` as a default block parameter
* At RubyKaigi 2022, [many attendees preferred `it` over `_1`](https://youtu.be/ajm3lr6Y9yE?si=d6Sry32Zlkvtj-Nc&t=3002), [Matz did not reject `it`... -
-
-
03:34 AM Feature #19430: Contribution wanted: DNS lookup by c-ares library
- I have created another ticket for executing `getaddrinfo(3)` in a dedicated pthread: #19965
-
- ## Problem
Currently, Ruby name resolution is not interruptible.
```
$ cat /etc/resolv.conf
nameserver 198.51.100.1
$ ./local/bin/ruby -rsocket -e 'Addrinfo.getaddrinfo("www.ruby-lang.org", 80)'
^C^C^C^C
```
If you set a ... -
- Applied in changeset commit:git|3f5ec5c8661748afb9cc3cbf1aff113d602e1fad.
----------
[DOC] Add NEWS about Range#reverse_each for beginless ranges [Feature #18515] -
-
- Ah, this warning is correct. `mutex_m` is removed from `rails/rails`.
https://github.com/rails/rails/commit/bcdeea5da7657375df21a856135ae7a66a8c3812
-
- The redundant warnings still happened.
```
$ RAILS_STRICT_WARNING=1 bin/test test/engine/test_test.rb
/Users/hsbt/.local/share/rbenv/versions/master/lib/ruby/gems/3.3.0+0/gems/minitest-5.20.0/lib/minitest.rb:3: warning: mutex_m whic... -
12:34 AM Feature #19744: Namespace on read
- In general I'm against npm-style multiple loading of dependencies, but I think I found a use case for this that I could get behind.
Would it be possible to use this features to load a Ractor-incompatible library inside a NameSpace ins... -
12:16 AM Revision 10272b27 (git): Use assert_separately to avoid defining `foo`
- When we eval the iseqs generated by prism, they can have side effects
like defining methods. In this case, we were defining the method "foo",
but other tests were expecting that the foo method would _not_ be
defined. -
-
-
-
-
- We changed ScopeNodes to point to their parent (previous) ScopeNodes.
Accordingly, we can remove pm_compile_context_t, and store all
necessary context in ScopeNodes, allowing us to access locals from
outer scopes. -
- This reverts commit fd87372a7482cbf7672c44ef95bc1dc3b00bab7c.
-
- Aha! Thank you, now it makes a lot more sense. While I still think that `1 + o` would be nice to have, at least I can see the rhyme and reason.
10/18/2023
-
- It's an estimator for application size and could be used as a
compilation heuristic later.
Co-authored-by: Maxime Chevalier-Boisvert <maxime.chevalierboisvert@shopify.com>
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com> -
11:03 PM Feature #19541: Proposal: Generate frame unwinding info for YJIT code
- That's awesome and I'm super looking forward to trying to profile our apps with `perf` once I finally get YJIT enabled! Assuming most of the hot code turns out to be JIT'd, this should definitely give a fairly good picture of the Ruby st...
-
- I added `--yjit-perf` on Ruby master https://github.com/ruby/ruby/pull/8697. It does not unwind Ruby frames in a single YJIT frame like DWARF would be able to do. But I think it's similar to how C functions are profiled with `--call-grap...
-
- > Just FTR, there is no other Ruby installed in the environment during build, so this is certainly not an issue.
OK, it explains why https://github.com/ruby/ruby/pull/8689 did not help. If that part is fine, I have nothing else to try... -
09:42 PM Bug #19921: TestYJIT#test_bug_19316 test failure
- k0kubun (Takashi Kokubun) wrote in #note-13:
> Subprocess tests like `test_yjit` in test-all generally seem to have a problem of picking a wrong Ruby
Just FTR, there is no other Ruby installed in the environment during build, so this... -
- I'm afraid we need a repro from you on CI (or anything I can exactly reproduce, like on Dockerfile) then. Subprocess tests like `test_yjit` in test-all generally seem to have a problem of picking a wrong Ruby, and it could be very much s...
-
- I tried commit:6c46ccf226bc6440743b51af713864c062eba27f but I see the same test failure.
-
- Can you try the latest master (newer than commit:7a3a98e2be69fd3fa68e6ee1afa43c3160f22254)? https://github.com/ruby/ruby/pull/8689 might help.
- 10:01 PM Revision 0ac6fb22 (git): Add test for many ivars
- Co-authored-by: John Hawthorn <john@hawthorn.email>
- 10:01 PM Revision a7032b80 (git): Revert "shape.h: Make attr_index_t uint8_t"
- This reverts commit e3afc212ec059525fe4e5387b2a3be920ffe0f0e.
-
09:13 PM Revision de076450 (git): [ruby/drb] Support :SSL{Min,Max}Version config options
- These are necessary to get the tests passing with LibreSSL 3.8.1+,
which dropped support for TLSv1.0 and TLSv1.1 for security reasons.
This updates the tests to use TLSv1.2 on OpenBSD. This is only
strictly necessary on OpenBSD 7.4+, b... -
- Co-authored-by: Alan Wu <alansi.xingwu@shopify.com>
- 07:34 PM Revision 58ee088b (git): Bump rustix from 0.38.2 to 0.38.19 in /yjit/bindgen
- Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.38.2 to 0.38.19.
- [Release notes](https://github.com/bytecodealliance/rustix/releases)
- [Commits](https://github.com/bytecodealliance/rustix/compare/v0.38.2...v0.38.19)
... - 07:20 PM Revision c46c529b (git): Update default gems list at 6873f96abc2a924b264b6ed3818b2f [ci skip]
-
07:19 PM Revision 6873f96a (git): [ruby/prism] Bump to version 0.15.1
- https://github.com/ruby/prism/commit/d906a8ceba
-
- Thanks @Eregon.
My main concern is that the gem author is not in control. You write your code, assume constants are stored in certain places, assume the nesting you are seeing with your eyes [*], and assume what constant resolution algo... -
- @fxn This proposal does not define multiple Object classes.
I think this proposal has limited value because if gems use this functionality they will multiply their memory footprint because each copy of a gem (with the same version) is... -
05:48 PM Feature #19931: to_int is not for implicit conversion?
- > So basically I thought that #to_i was for explicit conversion and #to_int for implicit conversion; is that not the case?
As far as I understand, it is exactly the case for operations that definitely expect an integer:
```ruby
o ... -
- byroot (Jean Boussier) wrote in #note-6:
> I have no idea how much code it would break though.
It can't *break* code. It can only cause broken code (as in my example) to suddenly work.
Eregon (Benoit Daloze) wrote in #note-7:
> ...
I t... -
- I think the coercion semantics are already quite complex, so we would need a convincing real-world use-case to make this more complicated.
-
04:35 PM Feature #19931: to_int is not for implicit conversion?
- To be fair, `+` does it for `to_str`:
```ruby
class Bar
def to_str
"bar"
end
end ... -
- sawa (Tsuyoshi Sawada) wrote in #note-2:
> Your description suggests a contrast between `to_int` and `to_i`, but while you showed a code example using `to_int`, you have not shown anything using `to_i`.
If using `to_i` for explicit c... -
- > 3. try the implicit conversion.
If I understood this correctly, that would allow doing things like
```ruby
1 + "1" # => 2
```
I hope that's not a direction we wanna follow. -
- The order of such calculations is now:
1. known classes (e.g., `Integer#+` knows about `Float`)
2. `coerce` on the RHS.
Otherwise raise an error.
Might consider adding another step there.
3. try the implicit conversion. -
01:10 AM Feature #19931: to_int is not for implicit conversion?
- Your description suggests a contrast between `to_int` and `to_i`, but while you showed a code example using `to_int`, you have not shown anything using `to_i`. Furthermore, actually replacing `to_int` in your code with `to_i` does not se...
- 04:51 PM Revision 4b909bdb (git): Update default gems list at 0f1e040068fac01856c5c4c0ba9530 [ci skip]
-
- https://github.com/ruby/prism/commit/ee429f8d50
-
- https://github.com/ruby/prism/commit/41c0e0e06e
-
- https://github.com/ruby/prism/commit/aca24b3a17
-
- https://github.com/ruby/prism/commit/e8114a786a
-
- https://github.com/ruby/prism/commit/1985a9ba51
-
- https://github.com/ruby/prism/commit/d469a56e7e
-
04:07 PM Bug #19932: Regexp o modifier freeze interpolation between method calls
- My apologies for my misunderstanding. Thanks for the detailed explanation. I now understand it's hard to do something else than the current behavior.
-
- I don't think the documentation could be made significantly clearer, though potentially it could benefit from an additional example. It's expected that the `o` modifier works the way it does, and does not generate a new regexp with each...
-
- I'm not sure I was clear.
It's not that clear reading the documentation that the "freeze" will continue to live outside the local scope. All examples are always outside a method definition. As for local variables I would expect `myreg... -
- It's expected and documented: https://docs.ruby-lang.org/en/master/regexp_rdoc.html#label-Interpolation+Mode
-
- Taken the following PoC:
```ruby
def poc(regexp)
hs = [
'azerty',
'azertyui',
'azertyuiop'
]
out = []
hs.each do |h|
out << h if /#{regexp}/.match?('azerty')
end
out
end
p poc('az')
p poc('w... -
-
- https://github.com/ruby/prism/commit/555551e8f2
-
- Right now, our Call{Operator,And,Or}WriteNode nodes represent two
different concepts:
```ruby
foo.bar += 1
foo[bar] += 1
```
These two statements are different in what they can support. The
former can never have arguments (or an openin... -
10:17 AM Revision ef3f9f1a (git): [rubygems/rubygems] Allow uninstalling multiple versions of same gem
- Currently, you can install multiple versions of the same gem just fine:
```
$ gem install simplecov:0.19.0 simplecov:0.22.0
Fetching simplecov-0.19.0.gem
Successfully installed simplecov-0.19.0
Parsing documentation for simplecov-0.19.0... -
-
09:10 AM Revision 46b8846b (git): Show backtraces when failed
- If `assert_equal(backtrace_locations.size, profile_frames.size)` in
`TestProfileFrames#test_matches_backtrace_locations_main_thread`
failed, we do not have enough information about it like that:
```
1) Failure:
TestProfileFrames#t... -
09:01 AM Revision f546fe15 (git): Loosen assertion for flaky weak references test
-
- ```
% docker run -it --rm rubylang/all-ruby env ALL_RUBY_SINCE=ruby-1.3 ./all-ruby -e 'inf = 1.0/0.0; 0.step(inf, 10) { |x| p x; break }'
ruby-1.3 /tmp/rbFgfjB4:1:in `/': divided by 0 (ZeroDivisionError)
... -
- Fixed at https://github.com/ruby/ruby/commit/ac8ece81f26f29dc2f9d77fcdb0620a51ba26f1e
-
- HEAD version of Bundler didn't install default gems if locked version is same version of default gems.
master of Ruby always uses default gems under the `RbConfig::CONFIG['rubylibdir']` because latest version of default gems installed... -
- Thanks always. I could reproduce that.
```
$ RAILS_STRICT_WARNING=1 bin/test test/engine/test_test.rb
/Users/hsbt/Documents/github.com/rails/rails/activesupport/lib/active_support/message_encryptor.rb:4: warning: base64 which will b... -
-
-
- 03:24 AM Revision be160859 (git): Bump actions/checkout from 4.1.0 to 4.1.1
- Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.0 to 4.1.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](http... -
-
-
- They are too unstable on the machine.
```
1) Failure:
TestRegexp#test_timeout_shorter_than_global [/home/chkbuild/chkbuild/tmp/build/20231018T230003Z/ruby/test/ruby/test_regexp.rb:1788]:
Expected |0.2 - 0.962938869| (0.762938869000000... -
- It seems saner to use RbConfig.ruby than using ruby in a random ancestor
directory. -
- Some people encounter an issue that test_yjit uses the installed Ruby
instead of the currently-running Ruby. It's fixed when they remove the
installed Ruby.
However, test_yjit should run the currently-running Ruby for testing
YJIT in su...
10/17/2023
-
- > note: `#[deny(clippy::redundant_locals)]` on by default
On Rust 1.73.0. -
- I may be wrong, but my understanding of it is that it's so the right hand side isn't always casted to the left-hand side type.
If `to_int` was invoked when doing `Integer + something`, then `1 + 1.5` would be `1 + (1.5).to_int` and wo... -
- While reviewing some implicit vs explicit conversion concepts, I discovered that arithmetic operations do not perform the implicit conversion I expected from #to_int
```ruby
o = Object.new
def o.to_int; 1; end
1 + o #TypeError
``... -
- What happens with the top-level constants defined by the interpreter? In particular, is `Object.object_id != ns1::Object.object_id != ns2::Object.object_id`?
-
-
-
-
05:50 PM Revision 5a3e8d2f (git): [ruby/prism] Ensure last encoding flag wins
- You can't encoding a string with more than one encoding so ensure that
the last one wins.
https://github.com/ruby/prism/commit/4182c988c9 -
-
- Previously, the version-controlled `cruby_bindings.inc.rs` file
contained the build-time artifact `id.h`, which nobu mentioned hinders
the goal of having fewer magic numbers in the repository.
Lookup the IDs YJIT needs on boot. It costs... -
- * YJIT: Add a cargo job for Arm64
* YJIT: Use command names as job names
They look more consistent with jobs that use the command name as a job
name, such as `make (check)`, `make (test-bundled-gems)`, etc.
* Remove .cirrus.yml -
- cf. https://ruby-doc.org/3.2.2/Regexp.html#class-Regexp-label-Character+Classes
> POSIX bracket expressions are also similar to character classes. They provide a portable alternative to the above, with the added benefit that they enco... -
-
12:58 PM Bug #19929 (Closed): Warnings for `mutex_m`, `drb` and `base64` appears while the gem spec has explicit dependencies
- Running some of Ruby on Rails unit test raises these warnings while it has explicit add_dependency entries https://github.com/rails/rails/blob/ae6fa7a048d0a0f79b0f8dd8566c7d499fd6f616/activesupport/activesupport.gemspec#L42-L45
```... -
- So that the tests can run without updating other than the programs.
-
-
11:54 AM Bug #19778: mkmf.rb pkg_config() interaction with RbConfig::CONFIG["cflags"]
- ruby_3_1 8563a144fda2fd130b672541a84d8bad0b6c4cd2 merged revision(s) bcb3247072e6973d0f6b50ca5fed238d5824bd28,fe0225ff4d5af8b1f54009727b39d0d9b821eea3.
- 11:51 AM Revision 8563a144 (git): merge revision(s) bcb3247072e6973d0f6b50ca5fed238d5824bd28,fe0225ff4d5af8b1f54009727b39d0d9b821eea3: [Backport #19778]
- [Bug #19778] Pass additional include options to INCFLAGS in common.mk
---
common.mk | 2 +-
configure.ac | 1 +
template/Makefile.in | 1 +
3 files changed, 3 insertions(+), 1 ... -
- ruby_3_1 a3e1444663005d3440b56c3a8e1b88bb28935912 merged revision(s) 96c5a4be7b0d72502001734770af0f4a735c544c.
- 11:30 AM Revision a3e14446 (git): merge revision(s) 96c5a4be7b0d72502001734770af0f4a735c544c: [Backport #19894]
- Fix memory leak in complemented method entries
[Bug #19894]
When a copy of a complemented method entry is created, there are two
issues:
1. IMEMO_FL_USER3 is not copied, so the complemented status is not
copied ... -
11:07 AM Revision 2a8ac8ea (git): [ruby/rdoc] Delay DidYouMean until NotFoundError#message is called
- https://github.com/ruby/rdoc/commit/b59ca2f981
-
-
- If `RUBY_MN_THREADS=1` is given, this patch shows `+MN` in
`RUBY_DESCRIPTION` like:
```
$ RUBY_MN_THREADS=1 ./miniruby --yjit -v
ruby 3.3.0dev (2023-10-17T04:10:14Z master 908f8fffa2) +YJIT +MN [x86_64-linux]
```
Before this patch, a ... -
-
04:10 AM Revision 908f8fff (git): [rubygems/rubygems] Don't hide original error in `after(:suite)` hook
- For some reason, Windows builds are failing quite consistently now.
However, it seems that errors are happening before this directory is
even created, so removal fails, hiding the original error.
Instead, don't let this removal fail due... -
02:30 AM Revision c782c6fd (git): Fix a typo [ci skip]
-
- https://github.com/ruby/prism/commit/0ea19ed823
10/16/2023
-
- `-d` option is basically same with `-h` (`--header`).
The difference is `-h` accept header file name.
Therefore remove `-d` option. -
- https://github.com/ruby/prism/commit/5d189ce33e
-
- https://github.com/ruby/prism/commit/bf9bdb9d82
-
- https://github.com/ruby/prism/commit/c7ef25a79a
-
- https://github.com/ruby/prism/commit/2b3d59f424
-
- This reverts commit 67a987f82bc8a2b7ec15581306873530821fcf9e.
-
- Amend ScopeNode to point to previous ScopeNode, and to have void*
pointers to constants and index_lookup_table
https://github.com/ruby/prism/commit/0534324312 -
- Besides my position on integrating with RG&B, I wanted to add my thoughts about the feature itself separately and how it might end up being used in gems.
## Usage in gems
I immediately imagine this feature being picked up by gems (... -
- From my side, I'm happy if this feature is added because as mentioned by @hsbt it'd be useful for us internally.
But I'm pretty strongly against providing any fuctionality that allows resolving and loading multiple versions of the sam... -
10:15 AM Feature #19744: Namespace on read
- byroot (Jean Boussier) wrote in #note-34:
> > Bundler and RubyGems (RG&B) should be considered in deciding on the acceptance or not of this feature.
> ...
You are absolutely right and maybe my previous statement of:
> Bundler and Ru... -
- > Bundler and RubyGems (RG&B) should be considered in deciding on the acceptance or not of this feature.
I'm just as doubtful as you on the desirability of being able to load two distinct versions of a dependency, but it is only one o... -
- Here are a few more thoughts from me that may have an impact on this, and I hope David will speak up as well:
Bundler and RubyGems (RG&B) should be considered in deciding on the acceptance or not of this feature. Why? Because the end-... -
- This comment previously specified TLS 1.2, but actually set the
version to TLS 1.0. LibreSSL 3.8.1 (included in OpenBSD 7.4)
dropped support for TLS 1.0/1.1 for security reasons, which
broke this test. Switch the test to use TLS 1.2 as... -
-
-
- Using the same `runs-os` across all jobs in the same workflow makes it
more likely to pass in case one of these runners is experiencing an
outage.
macos-arm-oss is generally not available outside ruby/ruby, so it's
fair to skip it for f... -
-
02:52 PM Bug #19921: TestYJIT#test_bug_19316 test failure
- vo.x (Vit Ondruch) wrote in #note-9:
> @jaruga could you please help with the reproducer. I think you are the best person 😇
Sure. Let me check this ticket later.
-
- * Fixed ConstantPathWriteNode
* FIxed FlipFlopNode - 12:22 PM Revision 6e88b72d (git): [PRISM] prevent underflow on popped splatarray (#8657)
- prevent underflow on popped splatarray
This only emits the splat array node when not popped -
- This message is displayed if STDIN is not a tty. The parallel test is
the case.
https://github.com/ruby/irb/commit/e26e90e3fb - 11:56 AM Revision 598af0e7 (git): Update default gems list at d1f781b0d49f16d996e3ba848f386e [ci skip]
-
- https://github.com/ruby/psych/commit/51cc86ff3f
-
- macos-arm-oss is unavailable for forked reopsitories other than
ruby/ruby. -
- To avoid creating literals for all combinations.
-
10:39 AM Revision 55a0d2c6 (git): [ruby/prism] Avoid unnecessary delete_prefix in LibRubyParser.resolve_type
- Only remove const prefix from non-pointer types.
https://github.com/ruby/prism/commit/97c9ffeb42 -
-
09:06 AM Bug #19928 (Closed): IPV6 nameserver issues: "Protocol not supported - socket(2) - udp"
- I get a similar error message to https://bugs.ruby-lang.org/issues/9477
The error message I see:
```
Errno::EPROTONOSUPPORT: Protocol not supported - socket(2) - udp
```
Similarly:
```
$ ruby -rresolv -e 'puts Resolv::DNS.new.... -
-
- Because of a trap of cmd.exe that `echo something > output` prints not
only "something" also the space before `>`, remove unexpected spaces. -
- https://github.com/rubygems/rubygems/commit/25304f3e8d
-
- https://github.com/rubygems/rubygems/commit/40989271dd
-
- https://github.com/rubygems/rubygems/commit/20460bc1ee
-
- https://github.com/rubygems/rubygems/commit/5f28a68d79
-
- The `lock` command is specifically designed to manage the lockfile, so
running it should take precedence over any "frozen" setting.
Besides that, "frozen" is not specifically designed as "lockfile cannot
be updated" but as "installation... -
- https://github.com/rubygems/rubygems/commit/bc233af4d2
- 04:51 AM Revision f37e9f42 (git): [rubygems/rubygems] [PathSupport] Simplify logic: If `Gem.default_dir` is writable, use it.
- I couldn't find a cross-platform way to check "can I create this directory?"
So I removed that, and went back to the original simpler logic of
"if the directory is writable, use it."
https://github.com/rubygems/rubygems/commit/3aa86a56db - 04:51 AM Revision 45a5ea5a (git): [rubygems/rubygems] Remove kludge that should be unnecessary.
- https://github.com/rubygems/rubygems/commit/f1d44ecb62
- 04:51 AM Revision 724398cc (git): [rubygems/rubygems] Remove outdated/incorrect comment.
- The function is also significantly simpler than it used to be,
to the point I'm not sure it needs a comment.
https://github.com/rubygems/rubygems/commit/29a0551e37 - 04:51 AM Revision 3f5da317 (git): [rubygems/rubygems] Rephrase "Defaulting to user installation" message.
- https://github.com/rubygems/rubygems/commit/b7c531347e
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net> -
- Move the check for unmet dependencies in lockfile just in time to be
able to re-resolve if unmet dependencies are found. -
- Although Ruby's hashes preserve the insertion order, the ordering of
method coverage results is inherently nondeterministic, because they
are collected using `ObjectSpace`.