December 2024 - ruby-talk - ml.ruby-lang.org

[ruby-talk:444600] [ANN] httpx 1.4.0 released
by Tiago Cardoso 18 Dec '24

18 Dec '24

httpx 1.4.0 has been released. ``` HTTPX.get("https://gitlab.com/honeyryderchuck/httpx <https://gitlab.com/honeyryderchuck/httpx>") ``` HTTPX is an HTTP client library for the Ruby programming language. Among its features, it supports: * HTTP/2 and HTTP/1.x protocol versions * Concurrent requests by default * Simple and chainable API * Proxy Support (HTTP(S), CONNECT tunnel, Socks4/4a/5) * Simple Timeout System * Lightweight by default (require what you need) And also: * Compression (gzip, deflate, brotli) * Streaming Requests * Authentication (Basic Auth, Digest Auth, AWS Sigv4) * Expect 100-continue * Multipart Requests * Cookies * HTTP/2 Server Push * H2C Upgrade * Automatic follow redirects * International Domain Names * GRPC * Circuit breaker * WebDAV * SSRF Filter * Datadog integration * Faraday integration * Webmock integration * Sentry integration Here are the updates since the last release: # 1.4.0 ## Features ### `:content_digest` plugin The `:content_digest` can be used to calculate the digest of request payloads and set them in the `"content-digest"` header; it can also validate the integrity of responses which declare the same `"content-digest"` header. More info under https://honeyryderchuck.gitlab.io/httpx/wiki/Content-Digest ## Per-session connection pools This architectural changes moves away from per-thread shared connection pools, and into per-session (also thread-safe) connection pools. Unlike before, this enables connections from a session to be reused across threads, as well as limiting the number of connections that can be open on a given origin peer. This fixes long-standing issues, such as reusing connections under a fiber scheduler loop (such as the one from the gem `async`). A new `:pool_options` option is introduced, which can be passed an hash with the following sub-options: * `:max_connections_per_origin`: maximum number of connections a pool allows (unbounded by default, for backwards compatibility). * `:pool_timeout`: the number of seconds a session will wait for a connection to be checked out (default: 5) More info under https://honeyryderchuck.gitlab.io/httpx/wiki/Connection-Pools ## Improvements * `:aws_sigv4` plugin: improved digest calculation on compressed request bodies by buffering content to a tempfile. * `HTTPX::Response#json` will parse payload from extended json MIME types (like `application/ld+json`, `application/hal+json`, ...). ## Bugfixes * `:aws_sigv4` plugin: do not try to rewind a request body which yields chunks. * fixed request encoding when `:json` param is passed, and the `oj` gem is used (by using the `:compat` flag). * native resolver: on message truncation, bubble up tcp handshake errors as resolve errors. * allow `HTTPX::Response#json` to accept extended JSON mime types (such as responses with `content-type: application/ld+json`) ## Chore * default options are now fully frozen (in case anyone relies on overriding them). ### `:xml` plugin XML encoding/decoding (via `:xml` request param, and `HTTPX::Response#xml`) is now available via the `:xml` plugin. Using `HTTPX::Response#xml` without the plugin will issue a deprecation warning. # 1.3.4 ## Bugfixes * webmock adapter: fix tempfile usage in multipart requests. * fix: fallback to binary encoding when parsing incoming invalid charset in HTTP "content-type" header. # 1.3.3 ## Bugfixes * fixing a regression introduced in 1.3.2 associated with the webmock adapter, which expects matchable request bodies to be strings # 1.3.2 ## Bugfixes * Prevent `NoMethodError` in an edge case when the `:proxy` plugin is autoloaded via env vars and webmock adapter are used in tandem, and a real request fails. * raise invalid uri error if passed request uri does not contain the host part (ex: `"https:/get"`) # 1.3.1 ## Improvements * `:request_timeout` will be applied to all HTTP interactions until the final responses returned to the caller. That includes: * all redirect requests/responses (when using the `:follow_redirects` plugin) * all retried requests/responses (when using the `:retries` plugin) * intermediate requests (such as "100-continue") * faraday adapter: allow further plugins of internal session (ex: `builder.adapter(:httpx) { |sess| sess.plugin(:follow_redirects) }...`) ## Bugfixes * fix connection leak on proxy auth failed (407) handling * fix busy loop on deferred requests for the duration interval * do not further enqueue deferred requests if they have terminated meanwhile. * fix busy loop caused by coalescing connections when one of them is on the DNS resolution phase still. * faraday adapter: on parallel mode, skip calling `on_complete` when not defined.

1 0

[ruby-talk:444599] [ANN] tobox 0.7.0 released
by Tiago Cardoso 18 Dec '24

18 Dec '24

The first version of tobox (v0.7.0) has been released. tobox implements the consumer side of the transactional outbox pattern, providing a simple way to configure your event handlers. * https://gitlab.com/honeyryderchuck/tobox * https://microservices.io/patterns/data/transactional-outbox.html tobox executes your handlers in a worker pool. The worker pool can be thread-based (default) or fiber-based. It uses the “SKIP LOCKED” SQL dialect to support concurrent polling for events from the database outbox table. It therefore only supports databases implementing it. As of today, that's: * PostgreSQL 9.5+ * MySQL 8+ * Oracle * Microsoft SQL Server It ships with plugins for sentry, datadog and zeitwerk. The plugin system is itself very simple, so you can add your own custom logic around event processing. It can be used as a background job processor, although it’s best used in tandem with an existing framework. Here are the updates since the last release: ## [0.7.0] - 2024-12-18 ### Features #### `:pg_notify` plugin The `:pg_notify` plugin is introduced, which leverages the PostgreSQL-only `LISTEN/NOTIFY` statements to asynchronously notify workers when there are new events to be processed (instead of regularly polling the database). #### `visibility_column` and `attempts_column` configuration The `visibility_column` configuration (default: `:run_at`) can be used not only to point to a differently named column, it can both point to either a timestamp column (used as a visibility timeout for events) or a boolean column (used to hide events from other transactions); using the latter will also disable exponential backoff in retries. The `attempts_column` configuration (default: `:attempts`) can be used to point to a differently named column, or, when set to `nil`, uncap retries. See when they can be used for in the readme recommendations section. ### Improvements #### fiber pool on async Support was removed for the `fiber_scheduler` gem, which is under-maintained, so the fiber worker pool will use an [async]( https://github.com/socketry/async) scheduler going forward. Functionality and APIs will be the same, but you'll have to add it to your Gemfile. ### Bugfixes * `datadog` integration: environment variables were wrongly named. ### Chore * `mutex_m` usage was removed. ## [0.6.1] - 2024-10-30 ### Improvements When possible, use `UPDATE FROM outbox RETURNING WHERE (SELECT id .... FOR UPDATE SKIP LOCKED` to fetch-and-update events in one go. ## [0.6.0] - 2024-10-25 ### Features #### Batch Events handling It's now possible to handle N events at a time. ```ruby # tobox.rb batch_size 10 # fetching 10 events at a time on("user_created", "user_updated") do |*events| # 10 events at most if events.size == 1 DataLakeService.user_created(events.first) else DataLakeService.batch_users_created(events) end end ``` This also supports raising errors only for a subset of the events which failed processing (more info in the README). ## [0.5.2] - 2024-10-22 ## Bugfixes * prevent `:max_connections` from being overidden. ### Improvements ## [0.5.1] - 2024-09-26 ### Improvements * Refactoring of management of event id which replaces `SELECT id IN (?)` resulting queries with `SELECT id = ?`. * Process shutdown is now more predictable, also in the grace period. * `grace_shutdown_timeout` is a new configuration, by default 5 (seconds).

1 0

[ruby-talk:444597] [ANN] png 1.3.1 Released
by Ryan Davis 16 Dec '24

16 Dec '24

png version 1.3.1 has been released! * home: <https://github.com/seattlerb/png> * bugs: <https://github.com/seattlerb/png/issues> * doco: <http://docs.seattlerb.org/png> PNG is an almost-pure-ruby PNG library. It lets you write a PNG without any C libraries. Changes: ### 1.3.1 / 2024-12-16 * 1 bug fix: * Fixed PNG::Color encoding errors on older ruby versions.

1 0

[ruby-talk:444596] The DCR Kids Programming Language Supports Live GUI Updates
by Andy Maleh 10 Dec '24

10 Dec '24

One of the requests I received at RubyConf 2024 for Glimmer DSL for LibUI (and other Glimmer desktop gems) is providing an editor that can update the GUI live as the programmer types code into it. I have built something like that before for a programming language for kids called DCR actually. https://raw.githubusercontent.com/AndyObtiva/dcr/master/images/dcr-demo.gif Continue reading blog post: https://andymaleh.blogspot.com/2024/12/the-dcr-kids-programming-language.ht… Check out DCR (Draw Color Repeat), which is built in Ruby using Glimmer DSL for SWT: https://github.com/AndyObtiva/dcr

1 0

[ruby-talk:444595] Montreal.rb Hack Night Solutions for Hunt The Wampus
by Andy Maleh 09 Dec '24

09 Dec '24

In November and December of 2024, Montreal.rb hosted 2 Ruby Hack Night meetups about building the historic computer game, Hunt The Wampus, which was a text-based adventure game developed by Gregory Yob in 1973. A GitHub repo has been provided with solutions, which include the Ruby code for the Model layer, a desktop GUI View layer, and a Rails Web Frontend View layer: https://andymaleh.blogspot.com/2024/12/montrealrb-hack-night-solutions-for.… https://raw.githubusercontent.com/AndyObtiva/hunt_the_wampus/refs/heads/sol…

1 0

[ruby-talk:444594] [ANN] graphics 1.1.2 Released
by Ryan Davis 07 Dec '24

07 Dec '24

graphics version 1.1.2 has been released! * home: <https://github.com/seattlerb/graphics> * rdoc: <http://docs.seattlerb.org/graphics> Graphics provides a simple framework to implement games and/or simulations and is designed to follow mathematical conventions, NOT game programming conventions. Particularly it: * Uses degrees. * Draws in quadrant 1 (0-90 degrees). * Right hand rule: 0 degrees is east, 90 is north, etc. These allow simple things like Trigonometry functions to work as expected. It means that all that stuff you were taught in grade school still work as intended. This makes one less thing you have to adjust when implementing your simulation. Changes: ### 1.1.2 / 2024-12-07 * 1 minor enhancement: * Bumped required ruby version. * 3 bug fixes: * Fixed bad copy/paste in setup script. (havenwood) * Fixed color handling in polygon. * Fixed frozen string literal in examples/editor.rb

1 0

[ruby-talk:444592] gem mysql2 doesn't work on windows 11
by Tom Reilly 05 Dec '24

05 Dec '24

Problem with Ruby gem mysql2 with windows ll libmysql.dll in \ruby\bin Single line program: require 'mysql2' With Ruby 3.3.6 gem mysql2 2.4.6 running windows 11 <internal:C:/Ruby33-x64/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require': Incorrect MySQL client library version! This gem was compiled for 10.8.8 but the client library is 3.4.1. (RuntimeError) from <internal:C:/Ruby33-x64/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require' from C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/mysql2-0.5.6/lib/mysql2.rb:36:in `<top (required)>' from <internal:C:/Ruby33-x64/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:141:in `require' from <internal:C:/Ruby33-x64/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:141:in `rescue in require' from <internal:C:/Ruby33-x64/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:135:in `require' from require.rb:1:in `<main>' <internal:C:/Ruby33-x64/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require': cannot load such file -- mysql2 (LoadError) from <internal:C:/Ruby33-x64/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require' from require.rb:1:in `<main>' >Exit code: 1 With: Ruvy version 3.2.2 x64 mingw WUCRT gem: ruby-mysql2 version 0.5.4 Windows 10 Program works as exxpected With: Ruvy version 3.2.2 x64 mingw WUCRT gem: ruby-mysql2 version 0.5.4 Windows 11 E:/Ruby32-x64/lib/ruby/3.2.0/socket.rb:68:in `connect': A socket operation encountered a dead network. - connect(2) for /tmp/mysql.sock (Errno::ENETDOWN) from E:/Ruby32-x64/lib/ruby/3.2.0/socket.rb:68:in `connect_internal' from E:/Ruby32-x64/lib/ruby/3.2.0/socket.rb:141:in `connect'Ruvy version 3.2.2 x64 mingw WUCRT Windows 10 from E:/Ruby32-x64/lib/ruby/3.2.0/socket.rb:1081:in `unix'Program works as expected from E:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/ruby-mysql-4.0.0/lib/mysql/protocol.rb:177:in `initialize' from E:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/ruby-mysql-4.0.0/lib/mysql.rb:195:in `new' from E:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/ruby-mysql-4.0.0/lib/mysql.rb:195:in `connect' from E:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/ruby-mysql2-0.5.4/lib/mysql2/client.rb:180:in `connect' from E:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/ruby-mysql2-0.5.4/lib/mysql2/client.rb:169:in `initialize' from ./require.rb:11:in `new' from ./require.rb:11:in `<main>' What is the problem with the ruby gem on windows 11? Any suggested fix please? Tom Reilly

2 1

[ruby-talk:444591] [ANN] minitest 5.25.4 Released
by Ryan Davis 03 Dec '24

03 Dec '24

minitest version 5.25.4 has been released! * home: <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> * vim: <https://github.com/sunaku/vim-ruby-minitest> * emacs: <https://github.com/arthurnn/minitest-emacs> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, 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/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. 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. Changes: ### 5.25.4 / 2024-12-03 * 1 bug fix: * Fix for must_verify definition if only requiring minitest/mock (but why?).

1 0

[ruby-talk:444590] [ANN] minitest 5.25.3 Released
by Ryan Davis 03 Dec '24

03 Dec '24

minitest version 5.25.3 has been released! * home: <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> * vim: <https://github.com/sunaku/vim-ruby-minitest> * emacs: <https://github.com/arthurnn/minitest-emacs> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, 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/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. 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. Changes: ### 5.25.3 / 2024-12-03 * 5 bug fixes: * Fixed assert_mock to fail instead of raise on unmet mock expectations. * Fixed assert_mock to take an optional message argument. * Fixed formatting of unmet mock expectation messages. * Fixed missing must_verify expectation to match assert_mock. * minitest/pride: Fixed to use true colors with *-direct terminals (bk2204)

1 0