General

Profile

aaronjensen (Aaron Jensen)

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 3 3

Activity

11/20/2024

04:08 PM Ruby Bug #20890: MacOS 15.1, Macbook pro 2024 m4, YJIT: Kernel Panic on network access, works w/o YJIT
maximecb (Maxime Chevalier-Boisvert) wrote in #note-19:
> - Which specific versions of the kernel is the bug happening on? @aaronjensen you said you can repro this on two M4 machines, can you report your Darwin kernel version and the mak...
aaronjensen (Aaron Jensen)

11/14/2024

04:12 AM Ruby Bug #20890: MacOS 15.1, Macbook pro 2024 m4, YJIT: Kernel Panic on network access, works w/o YJIT
> No. Modern kernels don't allow unprivileged programs like YJIT to crash them, period.
Makes sense to me. Does anyone have experience to getting Apple to pay attention or is this just a waiting game at this point?
aaronjensen (Aaron Jensen)
02:01 AM Ruby Bug #20890: MacOS 15.1, Macbook pro 2024 m4, YJIT: Kernel Panic on network access, works w/o YJIT
Unfortunate update from Apple:
> Thank you for being patient while the case was under review. I did receive a response from my escalation approval team about the matter at hand. Since it appears that the Macs are running 3rd party sof...
aaronjensen (Aaron Jensen)

11/13/2024

04:19 PM Ruby Bug #20890: MacOS 15.1, Macbook pro 2024 m4, YJIT: Kernel Panic on network access, works w/o YJIT
One more note is that you can still use preload if you disable Rail's enabling of YJIT (`config.yjit = false`). You can still use YJIT if you enable YJIT in `on_worker_boot`.
This may point to the problem specifically being enabling ...
aaronjensen (Aaron Jensen)
02:37 PM Ruby Bug #20890: MacOS 15.1, Macbook pro 2024 m4, YJIT: Kernel Panic on network access, works w/o YJIT
I can also reproduce this on two M4 Max Macbook Pros. For my app, it actually panics on app start (either during or right after preload) when I start with multiple workers. It crashes before it prints the individual workers, so I wondere... aaronjensen (Aaron Jensen)

03/18/2022

06:25 PM Ruby Feature #18648: ruby2_keywords and ... name arguments with impossible names
bkuhlmann (Brooke Kuhlmann) wrote in #note-2:
> Hey Aaron, in regards to `*`, `**`, and `&`, those are passthrough parameters (or bare parameters as I like to call them).
Ok, but why doesn't ... create them in this way? Why assign t...
aaronjensen (Aaron Jensen)
06:22 PM Ruby Feature #18648: ruby2_keywords and ... name arguments with impossible names
jeremyevans0 (Jeremy Evans) wrote in #note-1:
> This isn't a bug, it's currently expected behavior, even if it is a bit inconsistent. I'll switch this to feature, but if you would like the behavior changed, you'll need to respond with ...
aaronjensen (Aaron Jensen)
03:20 PM Ruby Feature #18648 (Feedback): ruby2_keywords and ... name arguments with impossible names
While investigating a break in a library using reflection, I realized that when ... is used or ruby2_keywords is used that Ruby will name arguments with their symbol, rather than leaving them unnamed. This test demonstrates the issue:
...
aaronjensen (Aaron Jensen)

01/13/2022

01:12 AM Ruby Bug #18474: 938e027c seems to have caused a regression in yield handling with concurrent-ruby
Thank you, this is helpful. I'm not sure whether or not concurrent-ruby is the right place to fix this. If someone were doing what your example does in a loop and then joining all of them and making that enumerable, it would be their res... aaronjensen (Aaron Jensen)

01/11/2022

04:06 PM Ruby Bug #18474 (Closed): 938e027c seems to have caused a regression in yield handling with concurrent-ruby
I'm sorry for the awful title, I don't know enough about what is going on to describe it better. From a debugging perspective it seems that a very specific set of circumstances causes a `begin` block to be jumped out of when a proc it is... aaronjensen (Aaron Jensen)

Also available in: Atom