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

[ruby-talk:444227] [ANN] debride 1.12.0 Released
by Ryan Davis 18 May '23

18 May '23

debride version 1.12.0 has been released! * home: <https://github.com/seattlerb/debride> * rdoc: <http://docs.seattlerb.org/debride> Analyze code for potentially uncalled / dead methods, now with auto-removal. Changes: ### 1.12.0 / 2023-05-18 * 1 major enhancement: * Massive overhaul of bin/debride_rm: faster, cleaner, can run a command between each deletion. * 2 minor enhancements: * Added alias_method and alias as pseudo-calls to source method. * Whitelist extended/included/prepended etc by default. * 6 bug fixes: * Added missing rails validation. * Bumped sexp_processor and ruby_parser dependencies. * Fix --exclude <dir> to properly exclude whole tree. * Fixed --exclude option to make it repeatable. * Fixed bug on anonymous block forwarding (eg fn(&)). (afuno) * Use RubyParser.new instead of RubyParser.for_current_ruby.

1 0

[ruby-talk:444229] Ruby2WASM Again: My first use case
by Philip Rhoades 18 May '23

18 May '23

People, I am looking at this idea again to solve a specific problem with a Chrome Extension. The history of this is: Text-based ToDo lists on DOS => yada yada for four decades . . Tab Management on Chromium-based Browsers. When the developer of “Tabs Outliner” became unresponsive I switched to “TabFern” which has been really nice and the developer is helpful but does not have much time leftover for my suggested enhancements. So, it would be nice if could develop a WASM replacement with Ruby. I attach a screenshot of a TabFern window (project) with the Ruby and WASM tabs I am currently looking at so you get the general idea of what I want. Suggestions about how to produce this (assuming it is a sensible and viable thing to do) are appreciated! Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

1 0

[ruby-talk:444225] Re: Generating XML
by Peter Hickman 18 May '23

18 May '23

So far building it by hand is no faster than using builder. Which I'm going to see as a plus for builder because it sure is easier to read I think that the real issue is building a big string piecemeal is where the time is being spent > -K0GVP] >

2 1

[ruby-talk:444221] [ANN] ruby_parser 3.20.1 Released
by Ryan Davis 17 May '23

17 May '23

ruby_parser version 3.20.1 has been released! * home: <https://github.com/seattlerb/ruby_parser> * bugs: <https://github.com/seattlerb/ruby_parser/issues> * rdoc: <http://docs.seattlerb.org/ruby_parser> ruby_parser (RP) is a ruby parser written in pure ruby (utilizing racc--which does by default use a C extension). It outputs s-expressions which can be manipulated and converted back to ruby via the ruby2ruby gem. As an example: def conditional1 arg1 return 1 if arg1 == 0 return 0 end becomes: s(:defn, :conditional1, s(:args, :arg1), s(:if, s(:call, s(:lvar, :arg1), :==, s(:lit, 0)), s(:return, s(:lit, 1)), nil), s(:return, s(:lit, 0))) Tested against 801,039 files from the latest of all rubygems (as of 2013-05): * 1.8 parser is at 99.9739% accuracy, 3.651 sigma * 1.9 parser is at 99.9940% accuracy, 4.013 sigma * 2.0 parser is at 99.9939% accuracy, 4.008 sigma * 2.6 parser is at 99.9972% accuracy, 4.191 sigma * 3.0 parser has a 100% parse rate. * Tested against 2,672,412 unique ruby files across 167k gems. * As do all the others now, basically. Changes: ### 3.20.1 / 2023-05-16 * 1 minor enhancement: * Fixes Sexp#line_max in parser for many constructs: paren_args, arrays of various sorts, calls, classes, modules, etc.

1 0

[ruby-talk:444220] [ANN] nokogiri v1.15.0 released
by Mike Dalessio 15 May '23

15 May '23

Nokogiri v1.15.0 has been released! This is primarily a feature release, with some small bugfixes. Full release notes are at https://github.com/sparklemotion/nokogiri/releases/tag/v1.15.0 but they are included below for your convenience. --- Nokogiri (鋸) makes it easy and painless to work with XML and HTML from Ruby. It provides a sensible, easy-to-understand API for reading, writing, modifying, and querying documents. It is fast and standards-compliant by relying on native parsers like libxml2, libgumbo, or xerces. --- ## 1.15.0 / 2023-05-15 ### Notes #### Ability to opt into system `malloc` and `free` Since 2009, Nokogiri has configured libxml2 to use `ruby_xmalloc` et al for memory management. This has provided benefits for memory management, but comes with a performance penalty. Users can now opt into using system `malloc` for libxml2 memory management by setting an environment variable: ``` sh # "default" here means "libxml2's default" which is system malloc NOKOGIRI_LIBXML_MEMORY_MANAGEMENT=default ``` Benchmarks show that this setting will significantly improve performance, but be aware that the tradeoff may involve poorer memory management including bloated heap sizes and/or OOM conditions. You can read more about this in the decision record at [`adr/2023-04-libxml-memory-management.md`](adr/2023-04-libxml-memory-management.md). ### Dependencies * [CRuby] Vendored libxml2 is updated to v2.11.3 from v2.10.4. For details please see: * https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.11.0 * https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.11.1 * https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.11.2 * https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.11.3 * [CRuby] Vendored libxslt is updated to v1.1.38 from v1.1.37. For details please see: * https://gitlab.gnome.org/GNOME/libxslt/-/releases/v1.1.38 ### Added * `Encoding` objects may now be passed to serialization methods like `#to_xml`, `#to_html`, `#serialize`, and `#write_to` to specify the output encoding. Previously only encoding names (strings) were accepted. [[#2774]( https://github.com/sparklemotion/nokogiri/issues/2774) [#2798]( https://github.com/sparklemotion/nokogiri/issues/2798) (Thanks, [@ellaklara](https://github.com/ellaklara)!) * [CRuby] Users may opt into using system `malloc` for libxml2 memory management. For more detail, see note above or [`adr/2023-04-libxml-memory-management.md`](adr/2023-04-libxml-memory-management.md). ### Changed * [CRuby] `Schema.from_document` now makes a defensive copy of the document if it has blank text nodes with Ruby objects instantiated for them. This prevents unsafe behavior in libxml2 from causing a segfault. There is a small performance cost, but we think this has the virtue of being "what the user meant" since modifying the original is surprising behavior for most users. Previously this was addressed in v1.10.9 by raising an exception. ### Fixed * [CRuby] `XSLT.transform` now makes a defensive copy of the document if it has blank text nodes with Ruby objects instantiated for them _and_ the template uses `xsl:strip-spaces`. This prevents unsafe behavior in libxslt from causing a segfault. There is a small performance cost, but we think this has the virtue of being "what the user meant" since modifying the original is surprising behavior for most users. Previously this would allow unsafe memory access and potentially segfault. [[#2800]( https://github.com/sparklemotion/nokogiri/issues/2800) ### Improved * `Nokogiri::XML::Node::SaveOptions#inspect` now shows the names of the options set in the bitmask, similar to `ParseOptions`. [[#2767]( https://github.com/sparklemotion/nokogiri/issues/2767) * `#inspect` and pretty-printing are improved for `AttributeDecl`, `ElementContent`, `ElementDecl`, and `EntityDecl`. * [CRuby] The C extension now uses Ruby's [TypedData API]( https://docs.ruby-lang.org/en/3.0/extension_rdoc.html#label-Encapsulate+C+D…) for managing all the libxml2 structs. Write barriers may improve GC performance in some extreme cases. [[#2808]( https://github.com/sparklemotion/nokogiri/issues/2808) (Thanks, [@etiennebarrie](https://github.com/etiennebarrie) and [@byroot]( https://github.com/byroot)!) * [CRuby] `ObjectSpace.memsize_of` reports a pretty good guess of memory usage when called on `Nokogiri::XML::Document` objects. [[#2807]( https://github.com/sparklemotion/nokogiri/issues/2807) (Thanks, [@etiennebarrie](https://github.com/etiennebarrie) and [@byroot]( https://github.com/byroot)!) * [CRuby] Users installing the "ruby" platform gem and compiling libxml2 and libxslt from source will now be using a modern `config.guess` and `config.sub` that supports new architectures like `loongarch64`. [[#2831]( https://github.com/sparklemotion/nokogiri/issues/2831) (Thanks, [@zhangwenlong8911](https://github.com/zhangwenlong8911)!) * [CRuby] HTML5 parser: * adjusts the specified attributes, adding `xlink:arcrole` and removing `xml:base` [[#2841](https://github.com/sparklemotion/nokogiri/issues/2841), [#2842](https://github.com/sparklemotion/nokogiri/issues/2842)] * allows `<hr>` in `<select>` [[whatwg/html#3410]( https://github.com/whatwg/html/issues/3410) [whatwg/html#9124]( https://github.com/whatwg/html/pull/9124) * [JRuby] `Node#first_element_child` now returns `nil` if there are only non-element children. Previously a null pointer exception was raised. [[#2808](https://github.com/sparklemotion/nokogiri/issues/2808), [#2844]( https://github.com/sparklemotion/nokogiri/issues/2844) * Documentation for `Nokogiri::XSLT` now has usage examples including custom function handlers. ### Deprecated * Passing a `Nokogiri::XML::Node` as the first parameter to `CDATA.new` is deprecated and will generate a warning. This parameter should be a kind of `Nokogiri::XML::Document`. This will become an error in a future version of Nokogiri. * Passing a `Nokogiri::XML::Node` as the first parameter to `Schema.from_document` is deprecated and will generate a warning. This parameter should be a kind of `Nokogiri::XML::Document`. This will become an error in a future version of Nokogiri. * Passing a `Nokogiri::XML::Node` as the second parameter to `Text.new` is deprecated and will generate a warning. This parameter should be a kind of `Nokogiri::XML::Document`. This will become an error in a future version of Nokogiri. * [CRuby] Calling a custom XPath function without the `nokogiri` namespace is deprecated and will generate a warning. Support for non-namespaced functions will be removed in a future version of Nokogiri. (Note that JRuby has never supported non-namespaced custom XPath functions.) ### Thank you! The following people and organizations were kind enough to sponsor @flavorjones or the Nokogiri project during the development of v1.15.0: * Götz Görisch (@GoetzGoerisch) * Airbnb (@airbnb) * Kyohei Nanba (@kyo-nanba) * Maxime Gauthier (@biximilien) * @renuo * @dbootyfvrt * YOSHIDA Katsuhiko (@kyoshidajp) * Homebrew (@Homebrew) * Hiroshi SHIBATA (@hsbt) * PuLLi (@the-pulli) * SiteLog GmbH (@sitelog-gmbh) * @zzak * Evil Martians (@evilmartians) * Ajaya Agrawalla (@ajaya) * Modern Treasury (@Modern-Treasury) * Danilo Lessa Bernardineli (@danlessa) We'd also like to thank @github who donate a ton of compute time for our CI pipelines! --- sha256 checksums: ``` 7dbb717c6abc6b99baa4a4e1586a6de5332513f72a8b3568a69836268c2e1f86 nokogiri-1.15.0-aarch64-linux.gem a60c373d86a9a181f9ace78793c4a91ab8fa971af3cce93e9fdf022cd808fe41 nokogiri-1.15.0-arm-linux.gem 41d312b2d4aa6b6750c2431a25c1bf25fb567bc1e0a750cf55dd02354967724b nokogiri-1.15.0-arm64-darwin.gem 51cc8d4d98473d00c0ee18266d146677161b6dd16f8c89cc637db91d47b87c63 nokogiri-1.15.0-java.gem 1b2d92e240d12ac0a27cb0618f52af6c405831fd339a45aaab265cecda1dc6ab nokogiri-1.15.0-x64-mingw-ucrt.gem 497840b3ed9037095fbdd1bf6f7c63d23efab5bcbb03b89d94a6ac8bcab3eda5 nokogiri-1.15.0-x64-mingw32.gem 5c26427f3cf28d8c1e43f7a7bc58e50298461c7bed5179456b122eefc2b2c5cb nokogiri-1.15.0-x86-linux.gem cbf93df1c257693dfe804c01252415ca7cb9d2452d6cebddf7a35a5dbeb3ea12 nokogiri-1.15.0-x86-mingw32.gem ca6cd6ed08e736063539c4aa7454391dfa4153908342e3d873f5bd9218d6f644 nokogiri-1.15.0-x86_64-darwin.gem 4b28e9151e884c10794e0acf4a6f49db933eee3cd90b20aab952ee0102a03b0c nokogiri-1.15.0-x86_64-linux.gem 0ca8ea2149bdaaae8db39f11971af86c83923ec58b72c519d498ec44e1dfe97f nokogiri-1.15.0.gem ```

1 0

[ruby-talk:444215] Is this the correct behaviour of `super`
by mark_young＠hotmail.com 15 May '23

15 May '23

I have been investigating a test failure triggered by upgrading selenium-webdriver from v4.9.0 to v4.9.1. This has lead me to produce the following test code that demonstrates the problem which occurs as an interaction between capybara and selenium. The test produces the following error > wrong number of arguments (given 2, expected 0..1) (ArgumentError) Here is some code that reproduces the error -----8<-----8<-----8<-----8<-----8<-----8<------8<-----8<-----8<----- require 'selenium/webdriver/atoms' require 'selenium/webdriver/common' require 'selenium/webdriver/version' module DeprecationSuppressor def initialize(*) puts 'in DeprecationSuppressor::initialize' super end end Selenium::WebDriver::Logger.prepend DeprecationSuppressor class Demo def initialize @logger = Selenium::WebDriver::Logger.new('Selenium', ignored: true) puts @logger.class end end Demo.new -----8<-----8<-----8<-----8<-----8<-----8<------8<-----8<-----8<----- Here is it failing ➜ ruby -v ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22] ➜ ruby demo.rb in DeprecationSuppressor::initialize /Users/my/.rvm/gems/ruby-3.2.2@test/gems/selenium-webdriver-4.9.1/lib/selenium/webdriver/common/logger.rb:51:in `initialize': wrong number of arguments (given 2, expected 0..1) (ArgumentError) The error is raised by the `super` call in the initialize method of the DeprecationSuppressor module. Naming the arguments in the initialize method fixes the problem e.g. -----8<-----8<-----8<-----8<-----8<-----8<------8<-----8<-----8<----- module DeprecationSuppressor def initialize(*args) puts 'in DeprecationSuppressor::initialize' super args end end Selenium::WebDriver::Logger.prepend DeprecationSuppressor -----8<-----8<-----8<-----8<-----8<-----8<------8<-----8<-----8<----- ➜ ruby demo.rb in DeprecationSuppressor::initialize Selenium::WebDriver::Logger I have also found that using `initialize(...)` works too. I've tested this on Ruby 3.2.2 and 3.1.4 For further context of the wider problem, here is the initialize method in selenium-webdriver 4.9.0 and 4.9.1 4.9.0: https://github.com/SeleniumHQ/selenium/blob/selenium-4.9.0/rb/lib/selenium/… 4.9.1: https://github.com/SeleniumHQ/selenium/blob/selenium-4.9.1/rb/lib/selenium/… The difference being that two more named arguments have been added Finally it looks to me as though the Capybara team are preparing to fix this in v3.9.1 (https://github.com/teamcapybara/capybara/issues/2666) My question is whether Ruby is behaving correctly? It seems to me that the `super` call in the initialize(*) method should work.

3 2

[ruby-talk:444208] Trivia: Debugging closures
by hmdne 12 May '23

12 May '23

If there's an interest in such posts, I will write more. The idea is that I will provide examples of lesser-known features of Ruby. Later on, I will do a longer write-up where I will provide a solution and explain it unless someone will do it before me :) Let's say I have a program I can't modify: ```ruby def gen_proc secret1 = rand secret2 = rand proc do p secret1 * secret2 nil end end my_proc = gen_proc binding.irb ``` It will launch an interactive Ruby console. When I type: ```ruby my_proc.() # .() is a shortcut of .call() ``` It will print some number, but each time I will type this expression, it will be the same number (until I relaunch the console). This number is derived from `secret1` and `secret2` variables. Those variables are stored somewhere - but where? What is the best way for me to obtain values of those variables? Do note that I can't modify the code :)

4 4

[ruby-talk:444211] rubygems.org malware notifications from google
by Corey Donohoe 12 May '23

12 May '23

Hi all, Someone was added to a project I worked on long ago earlier today, and google emailed me after delivery saying the noreply email from rubygems had been flagged for malware. Has anyone else seen anything similar? Am I a one-off or is there something wrong?

2 2

[ruby-talk:444203] [ANN] wxRuby3 0.9.0.beta-10 released
by martin＠corino.nl 11 May '23

11 May '23

For those of you (still) interested in building desktop GUI applications with Ruby this might be interesting. A first public beta of the newly revived wxRuby3 has been released. Like former editions of this project wxRuby3 aims to provide a native extension wrapping the popular C++ wxWidgets GUI framework libraries. If you are interested check this out: Github: https://github.com/mcorino/wxruby3 Rubygems: https://rubygems.org/gems/wxruby3

5 5

[ruby-talk:444198] Writing scripts in ruby
by Eike Dierks 08 May '23

08 May '23

Hi everyone at the ruby talk I want to bring forward, the art of writing scripts. Did you ever write a unix script? ruby was invented to write scripts. We are still stuck with that %x

4 4