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

[ruby-talk:444095] [ANN] packetgen 3.2.2 released
by Sylvain Daubert 23 Dec '22

23 Dec '22

packetgen 3.2.2 has been released. * home: <https://github.com/sdaubert/packetgen> * bugs: <https://github.com/sdaubert/packetgen/issues> * doc: <https://github.com/sdaubert/packetgen/wiki> PacketGen provides simple ways to generate, send and capture network packets. Supported protocols are: Ethernet, Dot11, Dot1x, ARP, IP, IPv6, GRE, ICMP, IGMP, ICMPv6, MLD, MLDv2, OSPFv2, OSPFv3, UDP, TCP, SNMP, DNS, EAP, BOOTP, DHCP, TFTP, HTTP and MDNS. Changes: ### 3.2.2 / 2022-12-23 * Add Header::HTTP::Headers#[] to access header through its name. * Add Header::HTTP::Headers#header? to check a header is embedded in HTTP::Headers. * Add Header::SNMP::VariableBindings#[] to access nth element in the binding list. * Add Header::SNMP::VariableBindings#size. * Add Header::DHCPv6::DUID#human_type. * Add Header::IP::SI#to_human and Header::IP::RA#to_human * Changed Types::Array#read so that it can now populate object from an array of hashes, and not only from a string. * Fixes: * Fix NameError in UnknownPacket#===. * Fix UnknownPacket#inspect (did nothing). * Fix Header::IP::Option.build when type is unknown. In such a case, type was not set in newly created option. * Fix Header::IP::Option#initialize: length was not set, and data parameter was not used.

1 0

[ruby-talk:444094] [ANN] rasn1 0.12.1 released
by Sylvain Daubert 23 Dec '22

23 Dec '22

rasn1 0.12.1 has been released. * home: <https://github.com/sdaubert/rasn1> * bugs: <https://github.com/sdaubert/rasn1/issues> * doc: <https://github.com/sdaubert/rasn1/wiki> RASN1 is a pure ruby ASN.1 library. RASN1 helps to create ASN.1 parsers and encoders. Changes: ### 0.12.1 / 2022-12-23 * Add tracing capability when parsing data to ease debugging

1 0

[ruby-talk:444093] [ANN] abstract_feature_branch 1.3.2
by Andy Maleh 22 Dec '22

22 Dec '22

abstract_feature_branch is one of the simplest and most minimalistic “Feature Flags” ruby gems out there. It enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store). GitHub: https://github.com/AndyObtiva/abstract_feature_branch RubyGem: https://rubygems.org/gems/abstract_feature_branch Change Log: 1.3.2: - Ensure better performance, fetch Redis Overrides at app/server startup time only by default while providing option to fetch live by setting AbstractFeatureBranch.feature_store_live_fetching to true - Do not automatically pre-init AbstractFeatureBranch.feature_store with Redis.new if it was nil as that is a bad default. - Fix issue with crashing when not including the connection_pool gem manually if needed with a version of redis older than 5 -- Andy Maleh LinkedIn: https://www.linkedin.com/in/andymaleh <https://www.linkedin.com/in/andymaleh> Blog: http://andymaleh.blogspot.com GitHub: http://www.github.com/AndyObtiva Twitter: @AndyObtiva <https://twitter.com/AndyObtiva>

1 0

[ruby-talk:444092] Unsuscribe
by Michel Revesche 22 Dec '22

22 Dec '22

Please unsuscribe me.

1 0

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

21 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 17 Dec '22

17 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 17 Dec '22

17 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