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

[ruby-talk:444163] [ANN] minitest 5.18.0 Released
by Ryan Davis 04 Mar '23

04 Mar '23

minitest version 5.18.0 has been released! * home: <https://github.com/seattlerb/minitest> * bugs: <https://github.com/seattlerb/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * 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.18.0 / 2023-03-04 * 2 major enhancements: * Added assert_pattern & refute_pattern for pattern matching. (flavorjones) * Added matching must_pattern_match & wont_pattern_match to minitest/spec. * 1 bug fix: * Support the new message format of NameError in Ruby 3.3 (mame)

1 0

[ruby-talk:444162] [ANN] ruby_parser 3.20.0 Released
by Ryan Davis 04 Mar '23

04 Mar '23

ruby_parser version 3.20.0 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.0 / 2023-03-04 * 1 major enhancement: * Added tentative 3.2 support. * 1 minor enhancement: * Change minimum ruby version to 2.6. (want higher) * 1 bug fix: * Fix up compare tasks for ruby 3.2 differences.

1 0

[ruby-talk:444157] Fixing Ruby gems installation part 2
by Felipe Contreras 01 Mar '23

01 Mar '23

Hi, This is the second part of my attempt at fixing gem installation, it's necessary because it's *not yet fixed*. https://felipec.wordpress.com/2023/02/27/fixing-ruby-gems-installation-part… The maintainers of rubygems continue to ignore my solution, despite being the only one that actually works. The patch is really simple: https://github.com/felipec/rubygems/commit/68c0127885bc80761eb948963f9d5733… And I created an Arch Linux package with the patch and proper overrides: https://aur.archlinux.org/packages/rubygems-user It works perfectly. It has been *twelve years* since the first issue regarding this was reported, hopefully it will get fixed before the end of this decade (could be fixed now if the maintainers simply applied my patch). Cheers. -- Felipe Contreras

2 2

[ruby-talk:444139] [ANN] Learning by Reversing: Native Gems, Parts 1 and 2
by Mohit Sindhwani 01 Mar '23

01 Mar '23

Hi Everyone, For a long time, I wanted to do a series of posts called "Learning by Reversing" where I look at something that exists and is useful, and try to work back and explain it. For this, my first series is about Native Gems in Ruby. So, I've picked a simple native Ruby gem called fast-polylines and am looking at all the code, how to develop it, how to test it, how it loads, how it works, etc. with the aim of helping people understand Native Ruby gems better. The first 2 parts are now online on my blog: * Part 1 - This covers the background to the gem we explore Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e1-native-gems/ * Part 2 - This goes into the details of how ruby loads the native gem and extension (and includes a nice sequence diagram of how all the bits happen together) Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e2-native-gems/ Future posts are planned to go into details like: * The interface between Ruby and C * The Makefile * A Makefile that also works on Windows * Running the specs * Running the performance benchmark * Enhancements: - Providing an executable - A gem that also works on JRuby - Making the gem ractor friendly - Patching an existing gem rather than a new module Comments on the posts or the plans welcome. Best regards, Mohit.

4 4

[ruby-talk:444156] Re: How to load ruby-openssl headers in a C extension
by Tiago Cardoso 27 Feb '23

27 Feb '23

Hi, thx for the suggestion. Unfortunately, it doesn't work with a bundled gem, at least in a mac: gems get distributed in .bundle packages, so: ```ruby spec = Gem::Specification.find_by_name("openssl") source_dir = File.join(spec.full_gem_path) Dir.glob(source_dir + "/*/**") => [] # ruby-install installs bundled gem extensions under /Users/tiagocardoso/src/ruby-3.2.1/.ext/x86_64-darwin21/ ``` I believe that Frank may be correct here, in that "openssl" does not declare its header files as external in extconf.rb . Thx, Tiago Ruby users (Avocadostore) <support(a)avocadostore.zendesk.com> escreveu no dia segunda, 27/02/2023 à(s) 21:24: > ##- Bitte geben Sie Ihre Antwort über dieser Zeile ein. -## > > Sie sind in dieser Supportanfrage (1955167) auf CC gesetzt. Antworten Sie > auf diese E-Mail, um Kommentare zur Anfrage hinzuzufügen. > > *Ruby users* > > 27. Feb. 2023, 22:24 MEZ > > Hi, > > In <CAD489_xmJUsZkPzzbhJPXi3naKn18fpt+Dj1_uVYf945p9FeZA(a)mail.gmail.com> > "[ruby-talk:444148] How to load ruby-openssl headers in a C extension" on > Mon, 27 Feb 2023 11:27:52 +0000, > Tiago Cardoso via ruby-talk <ruby-talk(a)ml.ruby-lang.org> wrote: > > > I'm writing a C extension which interfaces with ruby-openssl objects, and > > the openssl API. In the process, I'm needing access to some functions > which > > ruby-openssl declares in the header file: > > > https://github.com/ruby/openssl/blob/ea0a112a0c6a0498629e778af7991c9b4e3495… > > (example: ossl_raise). However, it's not clear to me how should I declare > > the #include in order to access it, for a header file coming from stdlib. > > Seems that ruby itself correctly places its header files (examples: > ruby.h, > > or ruby/io.h), but I don't see the openssl gem ones. > > You can use Gem::Specification for it in your extconf.rb: > > spec = Gem::Specification.find_by_name("openssl") > source_dir = File.join(spec.full_gem_path, "ext", "openssl") > $INCFLAGS += " -I#{source_dir}" > > See also: > > https://github.com/groonga/mysql2-replication/blob/main/ext/mysql2-replicat… > > Thanks, > -- > kou > ______________________________________________ > ruby-talk mailing list -- ruby-talk(a)ml.ruby-lang.org > To unsubscribe send an email to ruby-talk-leave(a)ml.ruby-lang.org > ruby-talk info -- > https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-talk.ml.ruby-lang.or… > > *Ruby users* > > 27. Feb. 2023, 21:28 MEZ > > On 2/27/23, Tiago Cardoso via ruby-talk <ruby-talk(a)ml.ruby-lang.org> > wrote: > > Hi Mohit, > > ... I want to access the headers of openssl "the ruby library", or more > specifically its C extension headers. > > So, you mean, e.g., these: > https://github.com/ruby/openssl/blob/master/ext/openssl/ > https://github.com/ruby/openssl/blob/master/ext/openssl/ossl.h > > It doesn't look like the extension installs those headers: > https://github.com/ruby/openssl/blob/master/ext/openssl/extconf.rb > > E.g., ruby/digest installs digest.h > https://github.com/ruby/digest/blob/master/ext/digest/extconf.rb > > $INSTALLFILES = { > "digest.h" => "$(HDRDIR)" > } if $extmk > ______________________________________________ > ruby-talk mailing list -- ruby-talk(a)ml.ruby-lang.org > To unsubscribe send an email to ruby-talk-leave(a)ml.ruby-lang.org > ruby-talk info -- > https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-talk.ml.ruby-lang.or… > > *Ruby users* > > 27. Feb. 2023, 20:34 MEZ > > Hi Mohit, > > Thx for the reply. "#include <openssl/ossl.h>" is to access headers from > openssl "the library", whereas I want to access the headers of openssl "the > ruby library", or more specifically its C extension headers. > > Both "#include <ruby/ruby.h>" and "#include <sys/time.h>" do not apply to > my use-case: the first is a header file from the ruby distribution, not an > stdlib, whereas the latter is a (non-ruby related) system library. > > Best regards, > Tiago > > Mohit Sindhwani <mo_mail(a)onghu.com> escreveu no dia segunda, 27/02/2023 > à(s) 16:35: > > Hi Tiago, > > On 2023-2-27 7:27 pm, Tiago Cardoso via ruby-talk wrote: > > I'm writing a C extension which interfaces with ruby-openssl objects, and > the openssl API. In the process, I'm needing access to some functions which > ruby-openssl declares in the header file: > https://github.com/ruby/openssl/blob/ea0a112a0c6a0498629e778af7991c9b4e3495… > (example: ossl_raise). However, it's not clear to me how should I declare > the #include in order to access it, for a header file coming from stdlib. > Seems that ruby itself correctly places its header files (examples: ruby.h, > or ruby/io.h), but I don't see the openssl gem ones. > > The beginning of my C file looks like: > > ```C > #include <ruby.h> > #include <openssl/evp.h> > > #include <pathto/openssl/ossl.h> // how to do this? > ``` > > What is the error that you are getting? I would have that it should just > work with "#include <openssl/ossl.h>" on the idea that it's relative to the > system include directory but I am still exploring how C native extensions > work but I thought it should have worked since I see other gems (e.g., > grpc) include other items like: > > #include <ruby/ruby.h> > #include <sys/time.h> > > Best regards, > Mohit. > > *Ruby users* > > 27. Feb. 2023, 12:28 MEZ > > Hi, > > I'm writing a C extension which interfaces with ruby-openssl objects, and > the openssl API. In the process, I'm needing access to some functions which > ruby-openssl declares in the header file: > https://github.com/ruby/openssl/blob/ea0a112a0c6a0498629e778af7991c9b4e3495… > (example: ossl_raise). However, it's not clear to me how should I declare > the #include in order to access it, for a header file coming from stdlib. > Seems that ruby itself correctly places its header files (examples: ruby.h, > or ruby/io.h), but I don't see the openssl gem ones. > > The beginning of my C file looks like: > > ```C > #include <ruby.h> > #include <openssl/evp.h> > > #include <pathto/openssl/ossl.h> // how to do this? > ``` > > Thx, > Tiago > Avocado Store GmbH > Cremon 32, 20457 Hamburg > avocadostore.de <https://www.avocadostore.de> - Eco Fashion & Green > Lifestyle > [image: Instagram] <https://www.instagram.com/avocadostore.de> > [image: Facebook] <https://de-de.facebook.com/avocadostore> > [image: Pinterest] <https://pinterest.com/avocadostore> > [image: TikTok] <https://www.tiktok.com/@avocadostore.de> > [image: LinkedIn] <https://www.linkedin.com/company/avocadostore> > > Eine E-Mail verursacht durchschnittlich 4 g CO2, mit Anhang bis zu 50 g. > Jährlich bedeutet das 135 kg CO2-Emissionen pro Kopf. Verringere deine > Emissionen, indem du nur notwendige E-Mails verschickst und regelmäßig > E-Mails löschst. > Registergericht: Amtsgericht Hamburg, HRB 113545 > Umsatzsteuer-Identifikationsnummer: DE270706065 > Geschäftsführung: Mimi Sewalski & Till Junkermann > [V03OR4-EQ4Z8] >

1 0

[ruby-talk:444148] How to load ruby-openssl headers in a C extension
by Tiago Cardoso 27 Feb '23

27 Feb '23

Hi, I'm writing a C extension which interfaces with ruby-openssl objects, and the openssl API. In the process, I'm needing access to some functions which ruby-openssl declares in the header file: https://github.com/ruby/openssl/blob/ea0a112a0c6a0498629e778af7991c9b4e3495… (example: ossl_raise). However, it's not clear to me how should I declare the #include in order to access it, for a header file coming from stdlib. Seems that ruby itself correctly places its header files (examples: ruby.h, or ruby/io.h), but I don't see the openssl gem ones. The beginning of my C file looks like: ```C #include <ruby.h> #include <openssl/evp.h> #include <pathto/openssl/ossl.h> // how to do this? ``` Thx, Tiago

4 4

[ruby-talk:444149] [ANN] Learning by Reversing: Native Gems, Part 3
by Mohit Sindhwani 27 Feb '23

27 Feb '23

Hi Everyone, I started on a series to learn by reversing a native Ruby gem. Part 3 is now published! The step continues the examination by seeing how we package and ensure that the native extension is actually built during installation. Also, why are there 2 Makefiles? Part 3 - How do we ensure that we have everything and that it actually gets built at installation? Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e3-native-gems/ The first 2 parts are also online on my blog: * Part 1 - This covers the background to the gem we explore Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e1-native-gems/ * Part 2 - This goes into the details of how ruby loads the native gem and extension (and includes a nice sequence diagram of how all the bits happen together) Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e2-native-gems/ Future posts are planned to go into details like: * The interface between Ruby and C * The Development Makefile and a Makefile that also works on Windows * Running the specs and the performance benchmark * Enhancements: - Providing an executable - A gem that also works on JRuby - Making the gem ractor friendly - Patching an existing gem rather than a new module Comments on the posts or the plans welcome. I'm @onghu on Twitter or @onghu@ruby.social on Mastodon if you're on either. Best regards, Mohit.

1 0

[ruby-talk:444142] Good URI.escape alternatives
by Gui Heurich 27 Feb '23

27 Feb '23

Hi list, I'm working on replacing URI.escape/unescape before moving a project to Ruby 3.x. I was wondering what most of you have used as alernatives and how they have worked for you. AFAIK, these are the options: CGI.escape URI.encode_www_form URI.encode_www_form_component Also, if you have any links to interesting posts, articles, videos about this, do send them through. Thanks! Guilherme anthropologist programmer code-anth.xyz Sent with Proton Mail secure email.

2 2

[ruby-talk:444146] [ANN] raindrops 0.20.1 - real-time stats for preforking Rack servers
by Eric Wong 25 Feb '23

25 Feb '23

raindrops is a real-time stats toolkit to show statistics for Rack HTTP servers. It is designed for preforking servers such as unicorn, but should support any Rack HTTP server on platforms supporting POSIX shared memory. It may also be used as a generic scoreboard for sharing atomic counters across multiple processes. * https://yhbt.net/raindrops/ * public mail box (no subscribers, no HTML mail): raindrops-public(a)yhbt.net * mail archives: https://yhbt.net/raindrops-public/ http://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/raind… imaps://yhbt.net/inbox.comp.lang.ruby.raindrops.0 nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.lang.ruby.raindrops imap://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.lang.ruby.raindrops.0 (.onion URLs require Tor) * git clone https://yhbt.net/raindrops.git * torsocks git clone http://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/raind… * https://yhbt.net/raindrops/NEWS.atom.xml Changes: raindrops 0.20.1 Stats for SO_REUSEPORT sockets are now handled properly. Thanks to Dale Hamel for the patches. Dale Hamel (2): Fix queue stats for sockets with SO_REUSEPORT Fix off by one error in test -- -_-

1 0

[ruby-talk:444137] [ANN] guess_os gem
by iloveruby 16 Feb '23

16 Feb '23

Hi, everybody! I'm developing a gem called "guess_os" to try guess local or remote (using SSH conn) OS. Could you try "guess_os" on your system an give me feedback, please! Installation: gem install guess_os Running command: guess_os Responds with ip? [ENTER] to guess your localhost. Thanks! :-) Enviado con [Proton Mail](https://proton.me/) correo electrónico seguro.

2 1