Hello
At the moment llm.rb lets you spawn a tool with a number of
different concurrency strategies: fiber, thread, async-task,
and ractor.
The first three are great for IO bound work, ractor is great
for CPU bound work but is not always easy to use.
Enter Kernel.fork
The fifth strategy is Kernel.fork backed by an IPC layer that
transports values between a parent and child. It is also usually
easier to use than ractors - at least for now.
With this change llm.rb makes it easy to execute your tools with
all the major concurrency strategies that Ruby supports, so you
can focus on solving problems and not implementing infrastructure
that is usually not easy to get right.
Check it out:
https://github.com/llmrb/llm.rb#readme
Robert
Hi
Yesterday I launched relay.app
Relay is a self-hostable LLM environment with support for OpenAI,
DeepSeek, Anthropic, xAI and zAI out of the box.
It has a minimal set of dependencies - built on Roda, Sequel, Falcon,
llm.rb, HTMX and web sockets.
It is intentionally simple to get started, you should be up and running
in under two minutes
gem install relay.app
relay setup
relay start
Check screenshots and more at https://github.com/llmrb/relay.app#readme
If you want an LLM you can extend, it's worth a look. You can drop your
own tools into ~/.relay/tools and have the LLM discover them automatically.
No LLM experience required.
Robert
minitest version 6.0.6 has been released!
* home: <https://minite.st/>
* code: <https://github.com/minitest/minitest>
* bugs: <https://github.com/minitest/minitest/issues>
* rdoc: <https://docs.seattlerb.org/minitest>
* clog: <https://github.com/minitest/minitest/blob/master/History.rdoc>
minitest provides a complete suite of testing facilities supporting
TDD, BDD, and benchmarking.
"I had a class with Jim Weirich on testing last week and we were
allowed to choose our testing frameworks. Kirk Haines and I were
paired up and we cracked open the code for a few test
frameworks...
I MUST say that minitest is *very* readable / understandable
compared to the 'other two' options we looked at. Nicely done and
thank you for helping us keep our mental sanity."
-- Wayne E. Seguin
minitest/test is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.
minitest/spec is a functionally complete spec engine. It hooks onto
minitest/test and seamlessly bridges test assertions over to spec
expectations.
minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn't replace your linear algorithm with an exponential
one!
minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P
minitest/test is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.
"Again, I can't praise enough the idea of a testing/specing
framework that I can actually read in full in one sitting!"
-- Piotr Szotkowski
Comparing to rspec:
rspec is a testing DSL. minitest is ruby.
-- Adam Hawkins, "Bow Before MiniTest"
minitest doesn't reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.
## Features/Problems:
* minitest/autorun - the easy and explicit way to run all your tests.
* minitest/test - a very fast, simple, and clean test system.
* minitest/spec - a very fast, simple, and clean spec system.
* minitest/benchmark - an awesome way to assert your algorithm's performance.
* minitest/pride - show your pride in testing!
* minitest/test_task - a full-featured and clean rake task generator.
* Incredibly small and fast runner, but no bells and whistles.
* Written by squishy human beings. Software can never be perfect. We will all eventually die.
Changes:
### 6.0.6 / 2026-04-30
* 2 bug fixes:
* Fix using assert_equal/same/nil w/ BasicObject by comparing w/ `nil == exp`. (mtasaka)
* Removed private Assertions#_where as it is no longer used.
