Richard Böhme
Richard Böhme
Hey! Sorry for not coming back to #32 yet! I was trying things out and stumbled around a really weird bug that I cannot explain. I extracted the following snippet...
Our main approach is to work on one spec from [ruby/spec](https://github.com/ruby/spec/tree/master/core/range) at a time, implementing as much of the spec as possible, then check it off the list: - [x]...
Due to [ruby/spec](https://github.com/ruby/spec) lacking specs for most of the CSV library, we want to provide our own specs (with the goal of upstreaming those to ruby/spec). Currently the following methods...
When working on `Enumerator::Lazy` I noticed, that the REPL does not support Fibers. The following Error will occur: ``` nat> [1,2,3].to_enum.each {} ruby: /home/richard/repos/natalie/include/natalie/fiber_value.hpp:120: void Natalie::FiberValue::create_stack(Natalie::Env*, int): Assertion `comparison_ptr <...
We experienced some deprecation warnings after upgrading one of our apps to Ruby 2.7.5. This patch removes all deprecation warnings occurring when running the tests of the cells gem.
When defining a record type, I expected the type checker to complain if an additional (non-defined) key was supplied by the user. Specifically I expected the following to fail type...
Using `#empty?` is a common pattern to check if a form object has any errors or not. For example this method is also used when calling `#present?`. It should return...
To avoid confusion with the setup of column collations, that is needed to use this gem, it should be as simple as using ```ruby class AddRankToPages < ActiveRecord::Migration[7.0] def change...
**Describe the bug** We noticed a lot of Puma-related errors in one of our production deployments while being attacked and we were wondering if Puma behaves correctly in this case....