I've just been analysing these recurring segfaults happening from time to time and landed on the bug report. The same combo stands: ruby-odbc and a connected db object at shutdown. Looking forward to a fix.chucke (Tiago Cardoso)
Thx for the patch, much cleaner than mine. Indeed I thought there must have been a cleaner fix, but I admit I was out of my depth.chucke (Tiago Cardoso)
A succession of crashes was observed on a particular workload from our app, involving recursive set operations, after upgrading it to ruby 4.0.6 . LLM was used to build a reproduction (shared in the description of the PR linked below), a...chucke (Tiago Cardoso)
* [Feature #13677] Add hostname to "Name or service not known (SocketError)" * PR open in github: https://github.com/ruby/ruby/pull/16918 * Changed message format as per suggestion in https://bugs.ruby-lang.org/issues/13677#note-12...chucke (Tiago Cardoso)
* [Feature #13677] Add hostname to "Name or service not known (SocketError)" * PR open in github: https://github.com/ruby/ruby/pull/16918 * Changed message format as per suggestion in https://bugs.ruby-lang.org/issues/13677#note-12...chucke (Tiago Cardoso)
This adds the following predicate methods to IPAddr objects: * `#multicast?`: whether the ip address is multicast * `#link_local_multicast?`: whether the ip address is a link-local multicast it also alias `IPAddr#link_local?` as `IPA...chucke (Tiago Cardoso)
> Fiber-local storages are inherited across Threads. Wow, that was really unexpected, I didn't know about that! I guess that would work for my use case. Is this specified or accidental behaviour? > ... Doesn't the same apply to `Th...chucke (Tiago Cardoso)
## Motivation At work, we've been dealing with the need of propagating context across threads. The use cases are several, ranging from propagating logging / observability context, region / database shards, etc, on worker threads for s...chucke (Tiago Cardoso)
The [httpx test suite has been reliably failing with a core dump on latest ruby 4](https://gitlab.com/os85/httpx/-/jobs/14559355119). The test suite runs on minitest with parallel mode turned on, although the issue can be reproduced ...chucke (Tiago Cardoso)
* [Feature [#13677](https://bugs.ruby-lang.org/issues/13677)]: Add more details to error "Name or service not known (SocketError)" * [Proposal PR](https://github.com/ruby/ruby/pull/16918) adding the host into the error message * ...chucke (Tiago Cardoso)
chucke (Tiago Cardoso)12:56 PM Ruby Bug #19865: Segfault when calling user signal handlers during VM shutdown