Activity
From 06/27/2024 to 07/03/2024
07/03/2024
-
11:40 PM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- BTW, IIUC, if we can use CET instead of the shadow stack, it's a far simpler and more efficient solution, so I'm stro...
-
11:39 PM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- Thanks, I agree with your proposed change.
-
12:10 AM Bug #18061 (Assigned): Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
-
11:01 PM Bug #20597: `eval('break if false')` should raise SyntaxError but retuns nil
- I submitted a pull request to fix this (but prism still needs a related fix) https://github.com/ruby/ruby/pull/11099
-
08:35 PM Bug #20606: Thread#thread_variable_get, Thread#thread_variable? and Thread#[] methods handle non-String/Symbol parameter values differently
- This change would be simple to implement, and I agree the fiber/thread variable inconsistency seems odd. There are s...
-
03:56 PM Bug #20606 (Closed): Thread#thread_variable_get, Thread#thread_variable? and Thread#[] methods handle non-String/Symbol parameter values differently
- The `Thread#thread_variable_get`, `Thread#thread_variable?` and `Thread#[]` methods handle the `key` parameter that i...
-
08:34 PM Bug #20607: Exception messages are inconsistent when thread-local variables are accessed
- I submitted a pull request to make the error message consistent: https://github.com/ruby/ruby/pull/11097
-
04:41 PM Bug #20607 (Closed): Exception messages are inconsistent when thread-local variables are accessed
- `Thread`'s methods to manipulate thread-local variables raise `TypeError` exceptions with slightly different messages...
-
06:26 PM Bug #20605 (Closed): PRs with backported fix for https://github.com/ruby/ruby/pull/11036 to Ruby 3.3 and 3.2
-
01:42 PM Bug #20605 (Closed): PRs with backported fix for https://github.com/ruby/ruby/pull/11036 to Ruby 3.3 and 3.2
- Hey! I work for Datadog on the Ruby profiler part of the [datadog (previously ddtrace)](https://github.com/datadog/dd...
-
06:21 PM Bug #20603 (Closed): Rails Active Job test gets segmentation fault
-
06:19 PM Bug #20599 (Closed): TypeError: #<BaseMailer:0x00000000008070> is not a symbol nor a string since 4cbc41d5e5cb6793174d5964975fdb4470323ca1 with YJIT enabled
-
12:10 AM Bug #20599 (Assigned): TypeError: #<BaseMailer:0x00000000008070> is not a symbol nor a string since 4cbc41d5e5cb6793174d5964975fdb4470323ca1 with YJIT enabled
-
03:39 PM Bug #20601: Configuration flags are not properly propagated to assembler
- kjtsanaktsidis (KJ Tsanaktsidis) wrote in #note-4:
> and in fact I would go a step furthre and delete `$ASFLAGS` in ... -
11:58 AM Bug #20601: Configuration flags are not properly propagated to assembler
- Just one more thing: I was worried for a moment that trying to assemble with `$CFLAGS` would cause problems if you ha...
-
11:47 AM Bug #20601: Configuration flags are not properly propagated to assembler
- OK, I poked at this a bit tonight. I have quite a few thoughts but they're kind of disorganised.
The short version o... -
08:54 AM Bug #20601: Configuration flags are not properly propagated to assembler
- Is something like that really needed? From my POV, the issue is that originally, there were `.s` files processed by A...
-
04:21 AM Bug #20601: Configuration flags are not properly propagated to assembler
- I think we should do what we did for the pac-ret stuff, that Florian recommended, right? Run tests against CFLAGS in ...
-
03:16 PM Feature #20470 (Closed): Extract Ruby's Garbage Collector
- Applied in changeset commit:git|51bd816517941798c63e587a5a9f3caf69cd510e.
----------
[Feature #20470] Split GC into ... -
02:31 PM Feature #20589 (Closed): Resize array in `rb_ary_freeze` and use `rb_ary_freeze` internally for arrays
- Closing given https://github.com/ruby/ruby/pull/11030 was merged yesterday.
However it caused some assertions fail... -
12:11 AM Bug #20462 (Assigned): Native threads are no longer reused
07/02/2024
-
09:53 PM Bug #20603: Rails Active Job test gets segmentation fault
- Confirmed b2b8306b46 addresses this issue. Thanks for the fix.
```
$ ruby -v
ruby 3.4.0dev (2024-07-02T18:48:43Z... -
05:37 PM Bug #20603: Rails Active Job test gets segmentation fault
- I opened a fix https://github.com/ruby/ruby/pull/11086
-
01:05 PM Bug #20603 (Closed): Rails Active Job test gets segmentation fault
- Rails Active Job test sometimes gets segmentation fault.
https://buildkite.com/rails/rails-nightly/builds/723#01906a... -
05:18 PM Bug #20604 (Rejected): Performance regression in C++ extensions due to lack of optimization flags by default since Ruby 2.7
- I found a significant performance regression in `sassc` gem when comparing Ruby 2.6 and later, that the extension is ...
-
12:42 PM Bug #20602 (Closed): RangeError: integer 128496650801200 too big to convert to 'int' without YJIT since cdf33ed5f37f9649c482c3ba1d245f0d80ac01ce
- I have opened https://bugs.ruby-lang.org/issues/20588 and the test case has been fixed via 4cbc41d5e5cb6793174d596497...
-
12:38 PM Bug #20601: Configuration flags are not properly propagated to assembler
- This might be the medicine:
~~~patch
$ git diff
diff --git a/template/Makefile.in b/template/Makefile.in
index ... -
12:24 PM Bug #20601 (Closed): Configuration flags are not properly propagated to assembler
- Looking into #18061, one of the issues is that the `.S` files are not processed with the correct flags. For example t...
-
11:24 AM Bug #20573: Warning.warn shouldn't be called for disabled warnings
- As a small note on this, it's typically better to check `$VERBOSE` level and if the category is enabled before even g...
-
06:00 AM Bug #20592: Interrupting Addrinfo causes Segmentation fault on alpine
- @nagachika @k0kubun When you backport this patch, please backport commit:d8c6e91748871ab2287d7703347847fe18a292d2 as ...
-
04:47 AM Misc #20600 (Closed): @ruby-lang.org has been migrated to Cloudflare
- @ruby-lang.org has been migrated to Cloudflare, because ruby-lang.org was migrated from Google Domains to Squarespace...
07/01/2024
-
11:45 PM Bug #20599: TypeError: #<BaseMailer:0x00000000008070> is not a symbol nor a string since 4cbc41d5e5cb6793174d5964975fdb4470323ca1 with YJIT enabled
- This issue does not reproduce since a2c27bae9653a817b4e5f699f421836f8f97410b .
However, similar issue like #20588 ha... -
05:24 PM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- vo.x (Vit Ondruch) wrote in #note-41:
> Given that [GCC documentation](https://gcc.gnu.org/onlinedocs/gcc/Instrument... -
04:53 PM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- And FTR, [this](https://github.com/gcc-mirror/gcc/blob/8088374a868aacab4dff208ec3e3fde790a1d9a3/gcc/config/i386/cet.h...
-
04:52 PM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- As can be seen, I am testing this with Ruby 3.3.2. The upstream situation is, however, already a bit different since ...
-
04:42 PM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- Forgot to mention that Ruby needs to be built with `--disable-yjit`, because Rust is another problem:
https://bugz... -
04:37 PM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- So I am experimenting with this simple patch:
~~~patch
diff --git a/coroutine/amd64/Context.S b/coroutine/amd64/C... -
05:13 PM Bug #20099: Ruby 3.3.0 segfaults on s390x musl libc (Alpine Linux) when built with -O3 (default optflags)
- I've tried to reproduce the bug on Linux One s390x machine(using docker image alpinelinux/alpine-gitlab-ci with ruby ...
-
11:35 AM Bug #20596 (Closed): [BUG] unexpected rb_parser_ary_data_type (0) for script lines
-
01:11 AM Bug #20596: [BUG] unexpected rb_parser_ary_data_type (0) for script lines
- Applied the patch to master branch https://github.com/ruby/ruby/pull/11076.
06/29/2024
-
03:48 PM Bug #20596: [BUG] unexpected rb_parser_ary_data_type (0) for script lines
- Just saw the same in Puma CI: https://github.com/puma/puma/actions/runs/9725211941/job/26842252268?pr=3418#step:4:115
06/28/2024
06/27/2024
-
11:58 PM Bug #20599 (Closed): TypeError: #<BaseMailer:0x00000000008070> is not a symbol nor a string since 4cbc41d5e5cb6793174d5964975fdb4470323ca1 with YJIT enabled
https://buildkite.com/rails/rails-nightly/builds/711#01905b80-6b82-460c-908d-c8bc7e69293a/1213-1221
### Steps to...-
11:52 PM Bug #20588: RangeError: integer 132186463059104 too big to convert to 'int' since cdf33ed5f37f9649c482c3ba1d245f0d80ac01ce with YJIT enabled
- It looks like 4cbc41d5e5cb6793174d5964975fdb4470323ca1 addresses this issue.
```
$ RUBY_YJIT_ENABLE=1 bin/test te... -
06:57 PM Bug #20598 (Closed): Corruption of internal encoding string
- Applied in changeset commit:git|176c4bb3c7db87ca5b0486012cb6a005105448c5.
----------
Fix corruption of internal enco... -
06:06 PM Bug #20598 (Closed): Corruption of internal encoding string
- GitHub PR: https://github.com/ruby/ruby/pull/11068
Just like #20595, Encoding#name_list and Encoding#aliases can h... -
02:53 PM Bug #20597 (Closed): `eval('break if false')` should raise SyntaxError but retuns nil
- These are all SyntaxError (Invalid break, compile error (SyntaxError))
~~~ruby
ruby -ce "break if false"
ruby -ce ... -
02:03 PM Bug #20596 (Closed): [BUG] unexpected rb_parser_ary_data_type (0) for script lines
- https://github.com/ruby/setup-ruby/actions/runs/9697443755/job/26761634004
```
/home/runner/.rubies/ruby-head/bin/b... -
01:47 PM Bug #20595 (Closed): Corruption of encoding name string
- Applied in changeset commit:git|c6a0d03649c686a537c1f513a1e32205ac6a6512.
----------
Fix corruption of encoding name... -
01:44 PM Misc #20013: Travis CI status
- As a note, by the Travis's above change, while people can run Travis by sending a pull-request to the ruby/* reposito...
-
12:11 PM Misc #20013: Travis CI status
- > I am working to get the list of the github accounts who contributed to the ruby/ruby, ruby/zlib and ruby/prism in t...
Also available in: Atom