- ruby-talk - ml.ruby-lang.org

[ruby-talk:444091] [ANN] tobox 0.3.0 released
by Tiago Cardoso 22 Dec '22

22 Dec '22

The first version of tobox (v0.3.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 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.3.0] - 2022-12-12 ### Features #### Inbox Implementation of the "inbox pattern", which ensures that events are processed to completion only once. ```ruby # create an inbox table and reference it create_table(:inbox) do column :id, :varchar, null: true, primary_key: true # ... create_table(:outbox) do column :inbox_id, :varchar foreign_key :inbox_id, :inbox # ... # tobox.rb inbox_table :inbox inbox_column :inbox_id # event production DB[:outbox].insert(event_type: "order_created", inbox_id: "order_created_#{ order.id}", .... DB[:outbox].insert(event_type: "billing_event_started", inbox_id: "billing_event_started_#{order.id}", .... ``` ## [0.2.0] - 2022-12-05 ### Features #### Ordered event processing When the outbox table contains a `:group_id` table (and the producer fills up events with it), then a group of events with the same `:group_id` will be processed one by one, by order of insertion. ```ruby # migration create_table(:outbox) do column :message_group_id, :integer # tobox.rb message_group_column :group_id # event production DB[:outbox].insert(event_type: "order_created", message_group_id: order.id, .... DB[:outbox].insert(event_type: "billing_event_started", message_group_id: order.id, .... # order_created handled first, billing_event_started only after ``` #### on_error_worker callback The config option `on_error_worker { |error| }` gets called when an error happens in a worker **before** events are processed (p.ex. when the database connection becomes unhealthy). You can use it to report such errors to an error reporting system (the `sentry` plugin relies on it). ```ruby # tobox.rb on_error_worker { |error| Sentry.capture_exception(error, hint: { background: false }) } ``` ### Bugfixes Thread workers: when errors happen which bring down the workers (such as database becoming unresponsive), workers will be restarted.

1 0

[ruby-talk:444090] [ANN] httpx 0.22.0 released
by Tiago Cardoso 21 Dec '22

21 Dec '22

httpx 0.22.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 * Datadog integration * Faraday integration * Webmock integration * Sentry integration Here are the updates since the last release: # 0.22.0 ## Improvements ### Happy Eyeballs v2 finalized Until now, httpx was issuing concurrent DNS requests, but it'd only start connecting to the first, and then on the following by the right order, but sequentially. `httpx` will now establish connections concurrently to both IPv6 and IPv4 addresses of a given domain; the first one to succeed terminates the other. Successful connection means completion of both TCP and TLS (when applicable) handshakes. ### HTTPX::Response::Body#encoding A new method, `#encoding`, can be called on response bodies. It'll return the encoding of the response payload. # 0.21.1 ## Bugfixes * fix: protecting tcp connect phase against low-level syscall errors * such as network unreachable, which can happen if connectivity is lost meanwhile. * native resolver: fix for nameserver switch not happening in case of DNS timeout. * when more than a nameserver was advertised by the system. ## Chore * Removing usage of deprecated `Random::DEFAULT.rand` (using `Random.rand` instead)-

1 0

[ruby-talk:444044] [ANN] hoe 4.0.0 Released
by Ryan Davis 18 Dec '22

18 Dec '22

hoe version 4.0.0 has been released! * home: <http://www.zenspider.com/projects/hoe.html> * code: <https://github.com/seattlerb/hoe> * bugs: <https://github.com/seattlerb/hoe/issues> * rdoc: <http://docs.seattlerb.org/hoe/> * doco: <http://docs.seattlerb.org/hoe/Hoe.pdf> * clog: <https://github.com/seattlerb/hoe/blob/master/History.rdoc> * other: <http://github.com/jbarnette/hoe-plugin-examples> Hoe is a rake/rubygems helper for project Rakefiles. It helps you manage, maintain, and release your project and includes a dynamic plug-in system allowing for easy extensibility. Hoe ships with plug-ins for all your usual project tasks including rdoc generation, testing, packaging, deployment, and announcement. See class rdoc for help. Hint: `ri Hoe` or any of the plugins listed below. For extra goodness, see: http://docs.seattlerb.org/hoe/Hoe.pdf Changes: ### 3.26.0 / 2022-10-20 * 2 minor enhancements: * Added warning to bundled minitest/test_task. * Removed dead rcov plugin and added (simple)cov plugin. * 1 bug fix: * Fixed test task load path issue, prepend Hoe.include_dirs to ensure they come first.

12 34

[ruby-talk:444085] Re: A simple question about arguments
by Henry R 18 Dec '22

18 Dec '22

> def tt (x=123) > puts x > end => :tt > tt 123 => nil > tt(456) 456 => nil The code above is the default argument I know. But this one, > def tt2 (x:123) > puts x 1> end => :tt2 > tt2 123 => nil > tt2(456) Traceback (most recent call last): 5: from /usr/bin/irb:23:in `<main>' 4: from /usr/bin/irb:23:in `load' 3: from /Library/Ruby/Gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>' 2: from (irb):10 1: from (irb):6:in `tt2' ArgumentError (wrong number of arguments (given 1, expected 0)) As you see it fails. But the following calling could work. > tt2(x:456) 456 => nil > tt2(:x=>456) 456 => nil what's the trick behind it? Thanks & regards, Henry

2 1

[ruby-talk:444064] is times() an async operation
by Henry R 18 Dec '22

18 Dec '22

for instance, 10.times do |s| puts s end 0 1 2 3 4 5 6 7 8 9 => 10 is the arguments block run in async mode? I have this question b/c my program quit earily. i don't know if it's due to somewhat async operations. the code is like (connection to rabbitmq), conn = Bunny.new conn.start ch = conn.create_channel exchange = ch.fanout("myfanout",:durable => true) 100.times do |s| exchange.publish(s.to_s) end It can't publish the entire 100 items to the broker, just some items. Thanks.

2 2

[ruby-talk:444083] [ANN] minitest-server 1.0.7 Released
by Ryan Davis 17 Dec '22

17 Dec '22

minitest-server version 1.0.7 has been released! * home: <https://github.com/seattlerb/minitest-server> * rdoc: <http://docs.seattlerb.org/minitest-server> minitest-server provides a client/server setup with your minitest process, allowing your test run to send its results directly to a handler. Changes: ### 1.0.7 / 2022-12-17 * 1 minor enhancement: * Bumped to minitest ~> 5.16 to get improved marshal handling.

1 0

[ruby-talk:444082] [ANN] hoe 4.0.1 Released
by Ryan Davis 17 Dec '22

17 Dec '22

hoe version 4.0.1 has been released! * home: <http://www.zenspider.com/projects/hoe.html> * code: <https://github.com/seattlerb/hoe> * bugs: <https://github.com/seattlerb/hoe/issues> * rdoc: <http://docs.seattlerb.org/hoe/> * doco: <http://docs.seattlerb.org/hoe/Hoe.pdf> * clog: <https://github.com/seattlerb/hoe/blob/master/History.rdoc> * other: <http://github.com/jbarnette/hoe-plugin-examples> Hoe is a rake/rubygems helper for project Rakefiles. It helps you manage, maintain, and release your project and includes a dynamic plug-in system allowing for easy extensibility. Hoe ships with plug-ins for all your usual project tasks including rdoc generation, testing, packaging, deployment, and announcement. See class rdoc for help. Hint: `ri Hoe` or any of the plugins listed below. For extra goodness, see: http://docs.seattlerb.org/hoe/Hoe.pdf Changes: ### 4.0.1 / 2022-12-17 * 1 bug fix: * Add extra checks to release_sanity to ensure history file is updated before release.

1 0

[ruby-talk:444061] A simple question about arguments
by Henry R 17 Dec '22

17 Dec '22

Sorry for this newbie question. For arguments to ruby methods, what's difference between these two? method(x:y) method(x=>y) Thanks

2 2

[ruby-talk:444043] [ANN] rodauth-oauth 1.0.0 released
by Tiago Cardoso 15 Dec '22

15 Dec '22

rodauth-oauth 1.0.0 has been released. rodauth-oauth is a rack-compatible toolkit for building OAuth 2.0 authorization servers, as well as OpenID Authentication Providers. rodauth-oauth is certified <https://openid.net/certification/> for the following profiles of the OpenID Connect™ protocol: Basic OP, Implicit OP, Hybrid OP, Config OP, Dynamic OP, Form Post OP. # as simple as rodauth do enable :oauth_authorization_code_grant # or enable :oidc end Among its features, it supports: * Authorization Code Grant * Refresh Token Grant * Implicit Grant * Client Credentials Grant * Device Code Grant * Token Revocation * Token Introspection * Auth Server Metadata * PKCE * Resource Indicators * JWT Access Tokens * Assertion Framework * SAML 2.0 Bearer Assertion Grant * JWT Bearer Assertion Grant * JWT Secured authorization requests * Dynamic Client Registration * OpenID * OpenID Discovery * OpenID Multiple Response types * OpenID Connect Dynamic Client Registration * OpenID Relying Party Initiated Logout It can also be used with Rails (via the "rodauth-rails" gem). Website: https://honeyryderchuck.gitlab.io/rodauth-oauth/ Documentation: https://honeyryderchuck.gitlab.io/rodauth-oauth/rdoc/ Wiki: https://gitlab.com/honeyryderchuck/rodauth-oauth/wikis/home CI: https://gitlab.com/honeyryderchuck/rodauth-oauth/pipeline These are the release notes since the last update: ## 1.0.0 (15/12/2022) ## Highlights rodauth-oauth is now [OpenID certified](https://openid.net/certification/) for the following certification profiles: * Basic OP * Implicit OP * Hybrid OP * Config OP * Dynamic OP * Form Post OP and passes the conformance tests for RP-Initiated Logout OP. The OIDC server used to run the test can be found [here](https://gitlab.com/os85/rodauth-oauth/-/blob/master/examples/oidc/aut… and deployed [here](https://rodauth-oauth-oidc.onrender.com). ### Breaking changes The full description of breaking changes, and suggestions on how to make the migration smoother, can be found in the [migration guide](https://gitlab.com/os85/rodauth-oauth/-/blob/6465b8522a78cf0037a55d3…. A short list of the main highlights: * Ruby 2.5 or higher is required. * `oauth_http_mac` feature removed. * `oauth_tokens` table (and resource) were removed (only `oauth_applications` and `oauth_grants`, access and refresh tokens are now properties of the latter). * access and refresh tokens hashed by default when stored in the database. * default oauth response mode is `"form_post"`. * oauth specific features require explicit enablement of respective features (no more `enable :oauth`) * refresh token policy is "rotation" by default * homepage url is no longer a client application required property. * OIDC RP-initiated logout extracted into `oidc_rp_initiated_logout` feature. ### Features The following helpers are exposed in the `rodauth` object: * `current_oauth_account` - returns the dataset row for the `rodauth` account associated to an oauth access token in the "authorization" header. * `current_oauth_application` - returns the dataset row for the oauth application associated to an oauth access token in the "authorization" header. When used in `rails` via `rodauth-rails`, both are exposed directly as controller helpers. #### `oauth_resource_server` plugin This plugin can be used as a convenience when configuring resource servers. #### JAR support for request_uri query param The `oauth_jwt_secured_authorization_request` plugin now supports a `request_uri` query param as well. #### OIDC features * The `oidc` plugin supports [essential claims](https://openid.net/specs/openid-connect-core-1_0.html#ClaimsParamet…, via the `claims` authorization request query parameter. * id token built with `"c_hash"` and `"at_hash"` claims when they should. ### Improvements * `:oauth_introspect` plugin: OAuth introspection endpoint exposes the token's `"username"` claim. * endpoint client authentication supports "client credentials grant" access tokens. * `acr_values_supported` exposed in the openid configuration. * `oauth_request_object_signing_alg_allow_none` enables `"none"` as an accepted request object signing alg when `true` (`false` by default). * OIDC `offline_access` supported. ### Bugfixes * fixed `oidc` calculation of `"auth_time"` claim. * JWT: "sub" is now always a string. * `response_type` is now an authorization request required parameter (as per the RFC). * `state` is now passed along when redirecting from authorization requests with `error`; * access token can now be read from POST body or GET query params (as per the RFC). * id token no longer shipping with claims with `null` value; * id token no longer encoding claims by default (only when `response_type=id_token`, as per the RFC). * support "JWT without kid" when doing jwt decoding for JWT tokens not generated in the provider (such as request objects). * Set `iss` and `aud` claims in the Userinfo JWT response. * Make sure errors are also delivered via form POST, when `response_mode=form_post`. * Authorization request now shows an error page when `response_type` or `client_id` are missing, or `redirect_uri` is missing or invalid; a new `"authorize_error"` template is invoked in such cases. * oidc: nonce present in id token when using the "id_token token" response type. * error parameter delivered in URL fragment when failing an implicit grant autorization request.

1 0

[ruby-talk:444042] How much speedup is caused by dispatch chains
by Faraaz Ahmad 15 Dec '22

15 Dec '22

Hi everyone! I'm writing a talk on how dispatch chains cause more cache hits in the RubyVM using this great article by Matthew Alp: https://mattalp.com/blog/dispatch-chains/. However, I'm unable to find any benchmarks on how much speedup is gained. Can someone please help me find any data on this my talk is tomorrow and I'm kinda panicking now haha Regards, Faraaz

1 0