* [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)
I get the point of avoiding mutating while iterating, but the point of `delete_if` is to mutate the array. there's nothing in its name hinting at it being based on the index, that's what `#delete_at` is for, so that's an implementation d...chucke (Tiago Cardoso)
The simplest example I can come up with: ```ruby $ar = ar = [1, 2, 3, 4, 5] def del(i) $ar.delete(i) end ar.delete_if { |e| e == 2 ? (del(e) && true) : false } p ar #=> [1, 4, 5], and it should be [1, 3, 4, 5] ```chucke (Tiago Cardoso)
I've been chasing an issue, which I believe is to with the recent introduction of the `fiber_interrupt` hook in ruby 4. As a reproduction I have the following snippet: ```ruby require "socket" require_relative "test/fiber/scheduler"...chucke (Tiago Cardoso)
* [Feature #21619] logger context API * Blog post detailing motivation [here](https://honeyryderchuck.gitlab.io/2025/11/12/context-missing-api-in-logger.html) * logger doesn't have a context API to enrich payload for structured log...chucke (Tiago Cardoso)
The logger gem is notoriously simple to use, but hard to extend. One can only observe a few of the gems that added tags / json / logstash formatting support to see the same functionality reimplemented in "same but different" ways. For...chucke (Tiago Cardoso)
Just adding my original public API suggestions, for visibility and further discussion by the core team. I propose that `URI::Generic` supports punycode decoding OOTB by relying on the current behaviour of `URI::Generic#hostname`, whic...chucke (Tiago Cardoso)
Proposal done as a [github issue](https://github.com/ruby/logger/issues/131) with [WIP implementation](https://github.com/ruby/logger/pull/132) for discussion purposes.chucke (Tiago Cardoso)
Not sure whether this is expected behaviour or not, but just leaving it here to start the debate on whether callbacks like `initialize_dup` are supposed to be called when a module or class is duped (the same happens with `initialize_copy...chucke (Tiago Cardoso)